aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/target.cxx
AgeCommit message (Collapse)AuthorFilesLines
2023-11-07Account for match options re-locking when checking if target is matchedBoris Kolpackov1-4/+8
2023-06-22Fix wraparound in task_count logicBoris Kolpackov1-2/+3
2023-06-02Temporarily turn null include error into warning for backwards compatBoris Kolpackov1-11/+19
2023-06-01Diagnose null include, operation-specific variable valuesBoris Kolpackov1-28/+46
While assigning null directly is unlikely, it's fairly easy via a variable expansion. Real-world example: ./: exe{tensor}: include = $config.Eigen.unsupported
2023-05-29Extend special match_rule() logic to all groups with dynamic targetsBoris Kolpackov1-1/+5
2023-05-29Explicit group: static membersBoris Kolpackov1-0/+38
2023-05-29Explicit group: syntax parsingBoris Kolpackov1-0/+13
2023-05-09Add support for dumping build system state in JSON format (GH issue #182)Boris Kolpackov1-1/+3
Specifically: 1. New --dump-format option. Valid values are `buildfile` and `json-v0.1`. 2. The --dump option now recognizes two additional values: `match-pre` and `match-post` to dump the state of pre/post-operations. The `match` value now only triggers dumping of the main operation.
2022-12-14Improve empty simple value to empty list of names reduction heuristicsBoris Kolpackov1-1/+1
Specifically, do not reduce typed RHS empty simple values for prepend/append and additionally for assignment provided LHS is typed and is a container.
2022-12-12Adapt to dir_iterator API changeKaren Arutyunov1-2/+22
2022-11-30Reserve targets, variables to avoid rehashingBoris Kolpackov1-0/+12
2022-11-29Fix backlink logic for target groupsBoris Kolpackov1-1/+2
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-18Complete low verbosity diagnostics reworkBoris Kolpackov1-34/+56
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-3/+4
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-13Switch to public/private variables modelBoris Kolpackov1-6/+13
Now unqualified variables are project-private and can be typified.
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov1-0/+2
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-27Allow search to find implied alias targetsBoris Kolpackov1-2/+7
Allowing this seems harmless since all the alias does is pull its prerequisites. And they are handy to use as metadata carriers.
2022-09-12Do not treat primary ad hoc group member as group for variable lookupBoris Kolpackov1-0/+18
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-04-19Use target recipe for auxiliary data storage during match-applyBoris Kolpackov1-1/+0
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-18Avoid locking target set if in load phaseBoris Kolpackov1-9/+22
2022-04-13Cache target base scope lookupsBoris Kolpackov1-10/+15
2022-04-06Add support for rule hintsBoris Kolpackov1-14/+14
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-14/+1
2022-03-11Add JSON format support for --structured-result option and info meta operationKaren Arutyunov1-3/+3
2022-03-10Fix operator<<(ostream,target_state)Karen Arutyunov1-0/+1
2022-03-07Fix operation-specific variables logic for inner/outer operationsBoris Kolpackov1-4/+10
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-13/+60
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.
2021-09-20Add support for disabling clean through target-prerequisite relationshipBoris Kolpackov1-10/+23
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-10/+19
2021-08-11Optimize process_libraries() some moreBoris Kolpackov1-5/+9
2021-05-28Tie loose ends in target type/pattern-specific matchingBoris Kolpackov1-5/+5
2021-05-28Clean default target type extension logicBoris Kolpackov1-15/+21
2021-05-28Make notion of name pattern explicit, fix various related loose endsBoris Kolpackov1-2/+3
2021-04-02Add support for propagating project environmentBoris Kolpackov1-0/+4
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-1/+1
2020-11-17Generalize dot escaping in target name rulesBoris Kolpackov1-45/+271
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-4/+8
2020-09-24Give hints for common causes of "no rule to update ..." errorBoris Kolpackov1-13/+9
2020-08-13Fix assertion failure in to_stream() for target key without extensionKaren Arutyunov1-2/+2
Also fix a similar assertion.
2020-07-17Add optimized derive_path_with_extension(), use in file_ruleBoris Kolpackov1-10/+19
2020-07-09Add support for ad hoc importationBoris Kolpackov1-67/+63
2020-06-29Add legal{} target type and config.install.legal variableBoris Kolpackov1-0/+13
This allows separation of legal files (LICENSE, AUTHORS, etc) from other documentation. For example: ./: ... doc{README} legal{LICENSE} $ b install ... config.install.legal=/usr/share/licenses/hello/
2020-06-29Use buildfile{} instead of build{} for target typeBoris Kolpackov1-1/+1
This feels like an oversight from transitioning to full names, like testscript{}, etc.
2020-06-09Handle empty target_key value (directory) in as_name()Boris Kolpackov1-4/+10
2020-06-02Add $target.process_path() analogous to $target.path()Boris Kolpackov1-1/+1
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-9/+5
2020-04-30Factor recipe to separate header/source filesBoris Kolpackov1-7/+0
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-0/+21
Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)"
2020-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov1-13/+13
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases.
generated by cgit v1.1 at 2024-11-14 07:46:12 +0000