aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/target.hxx
AgeCommit message (Collapse)AuthorFilesLines
2023-05-21Add support for dynamic target extraction in addition to prerequisitesBoris Kolpackov1-0/+4
This functionality is enabled with the depdb-dyndep --dyn-target option. Only the make format is supported, where the listed targets are added as ad hoc group members (unless already specified as static members). This functionality is not available in the --byproduct mode.
2023-03-02Replace deprecated std::aligned_storage with alignasBoris Kolpackov1-4/+4
Based on patch by Matthew Krupcale.
2022-11-30Reserve targets, variables to avoid rehashingBoris Kolpackov1-0/+4
2022-11-18Complete low verbosity diagnostics reworkBoris Kolpackov1-4/+4
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-2/+11
Unlike normal and ad hoc prerequisites, a post hoc prerequisite is built after the target, not before. It may also form a dependency cycle together with normal/ad hoc prerequisites. In other words, all this form of dependency guarantees is that a post hoc prerequisite will be built if its dependent target is built. See the NEWS file for details and an example.
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov1-15/+15
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-21Fix regression in dynamic dependency extraction, byproduct modeBoris Kolpackov1-0/+3
2022-09-12Do not treat primary ad hoc group member as group for variable lookupBoris Kolpackov1-0/+14
Note that we started with this semantics but it was changed in a commit on 2021-09-16 for reasons not entirely unclear but most likely due to target- specific variables specified for the group not being set on all the members. Which we have now addressed (see the previous commit). Note also that this new (old) semantics is not without its own drawbacks. Specifically, there is a bit of waste when the target-specific variable is really only meant for the recipe and thus setting it on all the members is unnecessary. For example: <{hxx ixx cxx}{options}>: cli{options} { options = ... } {{ # Use options. }} But this feels like a quality of implementation rather than conceptual issue. For example, we could likely one day address it by synthesizing a separate group target for ad hoc groups.
2022-06-29Make sure we generate common pkg-config file for only liba{}/libs{}Boris Kolpackov1-4/+10
2022-06-24Allow ad hoc rules not to list targets that are updated during matchBoris Kolpackov1-6/+27
For example, this allows a Qt moc rule not to list generated headers from libQtCore since they are pre-generated by the library.
2022-06-22Add missing match_data() destructorBoris Kolpackov1-0/+5
2022-04-20Replace match_extra::buffer with more general data storage facilityBoris Kolpackov1-2/+66
2022-04-19Use target recipe for auxiliary data storage during match-applyBoris Kolpackov1-41/+92
In particular, we now have separate auxiliary data storage for inner and outer operations.
2022-04-19Switch to using std::function for target::data_padBoris Kolpackov1-34/+80
2022-04-19Skip find() inside target_set::insert*() if target is unlikely to be thereBoris Kolpackov1-7/+19
2022-04-19Cache "recipe is group_action" information, clear recipes after executionBoris Kolpackov1-0/+1
2022-04-18Avoid locking target set if in load phaseBoris Kolpackov1-5/+15
2022-04-15Get rid of target::dynamic_type() virtual functionBoris Kolpackov1-35/+85
Instead of overriding this function, derived targets must now set the dynamic_type variable to their static_type in their constructor body.
2022-04-13Cache target base scope lookupsBoris Kolpackov1-5/+31
2022-04-07Rename {match,execute}() to *_sync(), add *_complete()Boris Kolpackov1-2/+2
In particular, the match() rename makes sure it doesn't clash with rule::match() which, after removal of the hint argument in simple_rule, has exactly the same signature, thus making it error-prone to calling recursively.
2022-04-06Add support for rule hintsBoris Kolpackov1-9/+60
A rule hint is a target attribute, for example: [rule_hint=cxx] exe{hello}: c{hello} Rule hints can be used to resolve ambiguity when multiple rules match the same target as well as to override an unambiguous match.
2022-03-31Use own type information instead of dynamic_cast in target::is_a()Boris Kolpackov1-6/+29
2022-03-07Add support for update=unmatch|match to ad hoc recipesBoris Kolpackov1-1/+2
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-12/+19
Note that the unmatch (match but do not update) and match (update during match) values are only supported by certain rules (and potentially only for certain prerequisite types). Additionally: - All operation-specific variables are now checked for false as an override for the prerequisite-specific include value. In particular, this can now be used to disable a prerequisite for update, for example: ./: exe{test}: update = false - The cc::link_rule now supports the update=match value for headers and ad hoc prerequisites. In particular, this can be used to make sure all the library headers are updated before matching any of its (or dependent's) object files.
2022-02-15Diagnose various misuses of library metadata protocolBoris Kolpackov1-1/+1
2022-02-09Don't use fallback file_rule to clean real targetsBoris Kolpackov1-0/+4
2022-02-09Don't skip empty see-through target groupsBoris Kolpackov1-5/+15
2022-01-11Work around VC14 bugBoris Kolpackov1-9/+0
2022-01-10Consider implied targets when resolving dynamic dependenciesBoris Kolpackov1-0/+9
2021-12-16Verify targets that alias same path are read-onlyBoris Kolpackov1-1/+6
2021-12-15Return stable imported target name from import_direct()Boris Kolpackov1-0/+5
2021-09-29Add notion of bundle amalgamation scopeBoris Kolpackov1-0/+6
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov1-1/+1
2021-09-20Add support for disabling clean through target-prerequisite relationshipBoris Kolpackov1-6/+2
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.
2021-09-15Do variable lookup in ad hoc target groupsBoris Kolpackov1-3/+6
2021-08-23Clear data in target::data() modifiersBoris Kolpackov1-2/+4
Currently we may end up resetting the data during the rule ambiguity detection.
2021-08-11Optimize process_libraries() some moreBoris Kolpackov1-2/+5
2021-06-08Get rid of special *{} wildcard target type notation in target type/patternsBoris Kolpackov1-1/+1
Explicit target{} should be used instead. Also, in this context, absent target type is now treated as file{} rather than target{}, for consistency with all other cases.
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-5/+14
An ad hoc pattern rule consists of a pattern that mimics a dependency declaration followed by one or more recipes. For example: exe{~'/(.*)/'}: cxx{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} If a pattern matches a dependency declaration of a target, then the recipe is used to perform the corresponding operation on this target. For example, the following dependency declaration matches the above pattern which means the rule's recipe will be used to update this target: exe{hello}: cxx{hello} While the following declarations do not match the above pattern: exe{hello}: c{hello} # Type mismatch. exe{hello}: cxx{howdy} # Name mismatch. On the left hand side of `:` in the pattern we can have a single target or an ad hoc target group. The single target or the first (primary) ad hoc group member must be a regex pattern (~). The rest of the ad hoc group members can be patterns or substitutions (^). For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} On the left hand side of `:` in the pattern we have prerequisites which can be patterns, substitutions, or non-patterns. For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} hxx{^'/\1/'} hxx{common} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} Substitutions on the left hand side of `:` and substitutions and non-patterns on the right hand side are added to the dependency declaration. For example, given the above rule and dependency declaration, the effective dependency is going to be: <exe{hello} file{hello.map>: cxx{hello} hxx{hello} hxx{common}
2021-06-08Redo fallback reverse operation machinery in ad hoc recipesBoris Kolpackov1-0/+14
2021-05-28Fix few Windows/VC compatibility issuesBoris Kolpackov1-2/+2
2021-05-28Clean default target type extension logicBoris Kolpackov1-0/+6
2021-05-28Make notion of name pattern explicit, fix various related loose endsBoris Kolpackov1-1/+1
2020-12-15Add explicit owns_lock() call to make Clang 3.7 happyBoris Kolpackov1-1/+1
2020-12-14Fix bug in create_new_target_locked()Karen Arutyunov1-1/+15
2020-12-11Add search_locked() versions of search() functionsBoris Kolpackov1-2/+2
2020-11-17Generalize dot escaping in target name rulesBoris Kolpackov1-3/+4
Now triple dot and escape sequence can appear almost anywhere in the target name (see target::split_name() for details).
2020-09-24Fix target declaration upgrade logicBoris Kolpackov1-8/+2
2020-09-24Give hints for common causes of "no rule to update ..." errorBoris Kolpackov1-11/+32
2020-08-10Allow holes in group_view arrayBoris Kolpackov1-0/+8