Skip to content

Commit

Permalink
mention the option to evolve any of the other tools
Browse files Browse the repository at this point in the history
  • Loading branch information
dirk-thomas committed Mar 20, 2017
1 parent a980b7c commit e99e8a9
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions articles/101_build_tool.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,12 +225,18 @@ The following items are possible extension points to provide custom functionalit
## Possible Approaches

In terms of flexibility neither of the existing build tools can already support the superset of features described in this article.
There are two different paths possible to reach the goal of a universal build tool:
There are multiple different paths possible to reach the goal of a universal build tool which fall into two categories:

- One approach is to incrementally evolve one of the existing tools to satisfy the described goals.
- Another approach would be to start "from scratch".

### Evolve catkin_make, catkin_make_isolated, or ament_tools

Since neither of these three build tools has the feature richness of `catkin_tools` it is considered strictly less useful to starting building upon one of these build tools.

### Evolve catkin_tools

One approach is to incrementally evolve one of the existing tools to satisfy the described goals.
Since `catkin_tools` is in many aspects the most complete build tool it should be one being evolved.
Since `catkin_tools` is in many aspects the most complete build tool it should be the one being evolved.
While `ament_tools` has a few features `catkin_tools` currently lacks (e.g. plain CMake support without a manifest, Windows support) the feature richness of `catkin_tools` makes it a better starting point.

The following items are highlighting some of the necessary efforts (not a complete list):
Expand Down

0 comments on commit e99e8a9

Please sign in to comment.