aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/algorithm.cxx
AgeCommit message (Collapse)AuthorFilesLines
2023-06-08Add support for buildfile importationBoris Kolpackov1-2/+2
2023-06-01Resolve (but disable for now) target_count issue in resolve_members()Boris Kolpackov1-22/+50
2023-05-31Provide implied configure_* and dist_* action registration for ad hoc recipesBoris Kolpackov1-27/+73
This makes it consistent with the existing ad hoc rules semantics.
2023-05-29Extend special match_rule() logic to all groups with dynamic targetsBoris Kolpackov1-24/+27
2023-05-29Disable counts verification if matched but not executed in resolve_members()Boris Kolpackov1-0/+7
2023-05-29Explicit group: static membersBoris Kolpackov1-10/+71
2023-04-05Allow creating context with bare minimum of initializationsBoris Kolpackov1-25/+25
This is used by bpkg to detect forwarded configurations without incurring the full context creation overhead.
2022-12-12Adapt to dir_iterator API changeKaren Arutyunov1-2/+1
2022-11-29Fix backlink logic for target groupsBoris Kolpackov1-107/+266
We used to backlink ad hoc group members both via the group and as individual members. And for explicit groups it was done only via individual members, which means it only works correctly if every member is individually updated. Now both types of groups are backlinked from the group target.
2022-11-23Take into account ad hoc recipes in rule::sub_match() (fixed GH issue #227)Boris Kolpackov1-61/+69
2022-11-18Complete low verbosity diagnostics reworkBoris Kolpackov1-12/+41
2022-11-16Initial low verbosity diagnostics reworkBoris Kolpackov1-13/+50
2022-10-20Don't create targets for non-existent source filesBoris Kolpackov1-2/+14
2022-10-19Handle operation-specific variable values in post hoc logicBoris Kolpackov1-1/+19
2022-10-19Minor tweaks to target_lock passing semanticsBoris Kolpackov1-2/+8
This should also get rid of the bogus -Wdangling-pointer issued by GCC 12.
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-50/+164
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-09-19Add target_lock::first to distinguish first lock of targetBoris Kolpackov1-7/+9
2022-09-12Do not treat primary ad hoc group member as group for variable lookupBoris Kolpackov1-4/+6
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-09-07Fix assert after cycle detection in ad hoc groupsBoris Kolpackov1-31/+31
2022-09-07Fix fsdir{} handling corner cases in ad hoc buildscript recipes/rulesdist-remapBoris Kolpackov1-2/+2
2022-07-13Work around "storing address of local variable" warning issued by GCC 12Boris Kolpackov1-1/+1
The warning is issued inside the target_lock's move constructor so we sidestep the whole thing by avoiding the call to the move constructor.
2022-06-23Minor enhancements to algorithmsBoris Kolpackov1-10/+49
2022-06-21Add --trace-{match,execute} optionsBoris Kolpackov1-1/+95
These options can be used to understand which dependency chain causes matching or execution of a particular target.
2022-04-19Use target recipe for auxiliary data storage during match-applyBoris Kolpackov1-4/+5
In particular, we now have separate auxiliary data storage for inner and outer operations.
2022-04-19Skip find() inside target_set::insert*() if target is unlikely to be thereBoris Kolpackov1-1/+2
2022-04-19Cache "recipe is group_action" information, clear recipes after executionBoris Kolpackov1-6/+12
2022-04-18Avoid locking target set if in load phaseBoris Kolpackov1-16/+22
2022-04-08Optimize update_during_match()Boris Kolpackov1-7/+14
2022-04-08Add hint-less rule match pass for non-perform meta-operations as fallbackBoris Kolpackov1-116/+143
2022-04-07Rename {match,execute}() to *_sync(), add *_complete()Boris Kolpackov1-59/+35
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-17/+13
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-10Add reverse_execute_prerequisites() variantBoris Kolpackov1-7/+102
2022-03-09Rename execute_wait() to execute()Boris Kolpackov1-1/+4
The old half-way semantics of execute() wasn't useful.
2022-03-09Parallel implementation of update_during_match_prerequisites()Boris Kolpackov1-22/+96
2022-03-08Improve performance of update during match for multiple targetsBoris Kolpackov1-0/+69
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-3/+65
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-09Don't use fallback file_rule to clean real targetsBoris Kolpackov1-2/+14
2022-02-09Add perform_clean_group_extra()Boris Kolpackov1-123/+137
2022-02-07Make match_inc_dependents() part of public APIBoris Kolpackov1-1/+1
2022-01-21Add search_new() and search_new_locked() variants of search()Boris Kolpackov1-0/+22
2021-09-16Fix diagnostics corner case in perform_clean_extra()Boris Kolpackov1-5/+5
2021-08-05Avoid normalizing likely already normalized directories in search_existing()Boris Kolpackov1-1/+8
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-60/+102
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-13/+30
2021-05-12Keep phase locked while working own queueBoris Kolpackov1-11/+5
2021-04-02Add support for propagating project environmentBoris Kolpackov1-25/+51
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-2/+2
2020-12-14Fix bug in create_new_target_locked()Karen Arutyunov1-1/+1
2020-12-11Add search_locked() versions of search() functionsBoris Kolpackov1-0/+11
2020-12-03Add match_rule() in addition to match_recipe()Boris Kolpackov1-6/+2