search

craftr-build / craftr-build-4.x

Frontend for the Craftr build framework.
https://craftr-build.github.io/craftr/
Other
60 stars 14 forks source link

Add option to exclude a Target from the default build #37

Closed NiklasRosenstein closed 8 years ago

NiklasRosenstein commented 8 years ago

Craftr generates a default <target> [<target> [...]] declaration at the end of a ninja build file. There should be an option exclude a target from this declaration, so it will only be built if another target depends on it or if it is explicitly targeted when calling craftr -b <target> or ninja <target>.

winksaville commented 8 years ago

YES!!!

On Wed, Dec 16, 2015 at 4:46 AM Niklas Rosenstein notifications@github.com wrote:

Closed #37 https://github.com/craftr-build/craftr/issues/37 via 3c3031d https://github.com/craftr-build/craftr/commit/3c3031d923c2d1d9a847d6e857cfa137af82b813 .

— Reply to this email directly or view it on GitHub https://github.com/craftr-build/craftr/issues/37#event-493419131.

NiklasRosenstein commented 8 years ago

Note that since Craftr 0.20.0, Targets in the "console" pool have never been added to that default statement in ninja. Now that the Target.explicit attribute was added, it can be used to exclude the target without setting the pool to "console"

winksaville commented 8 years ago

I ran into a problem with "console" when I was using CMake, so this sounds good.

On Wed, Dec 16, 2015 at 7:17 AM Niklas Rosenstein notifications@github.com wrote:

Note that since Craftr 0.20.0, Targets in the "console" pool have never been added to that default statement in ninja. Now that the Target.explicit attribute was added, it can be used to exclude the target without setting the pool to "console"

— Reply to this email directly or view it on GitHub https://github.com/craftr-build/craftr/issues/37#issuecomment-165137894.