diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2021-09-20 15:59:39 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2021-09-20 15:59:39 +0200 |
| commit | b7cb7f5510de019527f2a7b9e3f81dbb9813b5d9 (patch) | |
| tree | b204239436d477224a8664c82d8cf08a9629a504 /libbuild2/target.hxx | |
| parent | ab978916ef5d3a8f876953697c6eb9cdeedbc998 (diff) | |
Add support for disabling clean through target-prerequisite relationship
Our current semantics is to clean any prerequisites that are in the same
project (root scope) as the target and it may seem more natural to rather only
clean prerequisites that are in the same base scope. While it's often true for
simple projects, in more complex cases it's not unusual to have common
intermediate build results (object files, utility libraries, etc) reside in
the parent and/or sibling directories. With such arrangements, cleaning only
in base (even from the project root) may leave such intermediate build results
laying around (since there is no reason to list them as prerequisites of any
directory aliases). So we clean in the root scope by default but now any
target-prerequisite relationship can be marked not to trigger a clean with the
clean=false prerequisite-specific value.
Diffstat (limited to 'libbuild2/target.hxx')
| -rw-r--r-- | libbuild2/target.hxx | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/libbuild2/target.hxx b/libbuild2/target.hxx index 8193f35..a5940ab 100644 --- a/libbuild2/target.hxx +++ b/libbuild2/target.hxx @@ -874,15 +874,11 @@ namespace build2 uint8_t unmark (const target*&); - // Helper for dealing with the prerequisite inclusion/exclusion (the - // 'include' buildfile variable, see var_include in context.hxx). + // Helper for dealing with the prerequisite inclusion/exclusion (see + // var_include in context.hxx). // // Note that the include(prerequisite_member) overload is also provided. // - // @@ Maybe this filtering should be incorporated into *_prerequisites() and - // *_prerequisite_members() logic? Could make normal > adhoc > excluded and - // then pass the "threshold". - // include_type include (action, const target&, |