aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/target.ixx
AgeCommit message (Collapse)AuthorFilesLines
2023-11-17Add pre-condition assert to target::newer()Boris Kolpackov1-0/+2
2023-11-16Fix target::group_state() for unmatched ad hoc group membersBoris Kolpackov1-3/+13
2023-11-07Account for match options re-locking when checking if target is matchedBoris Kolpackov1-9/+21
2023-11-01Add support for adjusting match options of post hoc prerequisitesBoris Kolpackov1-0/+1
2023-11-01Add notion of match optionsBoris Kolpackov1-1/+3
Now, when matching a rule, the caller may request a subset of the full functionality of performing an operation on a target. This is achieved with match options.
2023-06-22Fix wraparound in task_count logicBoris Kolpackov1-7/+8
2023-05-29Explicit group: dynamic membersBoris Kolpackov1-2/+7
2023-05-29Explicit group: static membersBoris Kolpackov1-2/+2
2022-07-19Fix bug in target::matched()Boris Kolpackov1-1/+6
2022-04-20Replace match_extra::buffer with more general data storage facilityBoris Kolpackov1-3/+2
2022-04-19Cache "recipe is group_action" information, clear recipes after executionBoris Kolpackov1-4/+7
2022-04-15Get rid of target::dynamic_type() virtual functionBoris Kolpackov1-10/+5
Instead of overriding this function, derived targets must now set the dynamic_type variable to their static_type in their constructor body.
2022-04-08Optimize update_during_match()Boris Kolpackov1-1/+3
2022-04-06Add support for rule hintsBoris Kolpackov1-1/+86
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-07Add support for update=unmatch|match to ad hoc recipesBoris Kolpackov1-1/+6
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-3/+15
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-7/+14
2022-02-11Remove unnecessary header inclusionsBoris Kolpackov1-3/+4
2022-02-09Don't skip empty see-through target groupsBoris Kolpackov1-0/+19
2022-01-06Factor reusable code to target_key::effective_name()Boris Kolpackov1-0/+43
2021-12-16Verify targets that alias same path are read-onlyBoris Kolpackov1-2/+2
2021-09-20Add support for disabling clean through target-prerequisite relationshipBoris Kolpackov1-16/+4
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-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-0/+16
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}
2020-12-14Fix bug in create_new_target_locked()Karen Arutyunov1-1/+19
2020-12-03Fix bug in target::has_group_prerequisites()Boris Kolpackov1-1/+1
2020-08-10Allow holes in group_view arrayBoris Kolpackov1-8/+27
2020-07-17Fix race in path/mtime assignment and file_rule::match()Boris Kolpackov1-0/+15
2020-07-17Add optimized derive_path_with_extension(), use in file_ruleBoris Kolpackov1-1/+1
2020-06-10Reorder inline function definitions to help MinGW GCCBoris Kolpackov1-7/+7
2020-06-08Hash ad hoc prerequsites for ad hoc recipe change detectionBoris Kolpackov1-3/+6
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-3/+14
2020-04-30Rename target::member to target::adhoc_memberBoris Kolpackov1-6/+6
2020-04-30Factor recipe to separate header/source filesBoris Kolpackov1-0/+3
2020-04-27Get rid of warningsBoris Kolpackov1-0/+28
2020-03-20Add ability to query whether target has been matched for actionBoris Kolpackov1-0/+17
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-29Add sanity checkBoris Kolpackov1-1/+1
2019-11-18Add couple of sanity checksBoris Kolpackov1-0/+4
2019-10-02Allow iterating over group prerequisites during executeBoris Kolpackov1-1/+17
2019-08-23Introduce notion of build contextBoris Kolpackov1-9/+38
All non-const global state is now in class context and we can now have multiple independent builds going on at the same time.
2019-08-01Fix linkage failure due to inline functions defined in ↵Karen Arutyunov1-2/+2
libbuild2/algorithm.ixx and referred from libbuild2/target.txx
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+496