aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/rule.hxx
AgeCommit message (Collapse)AuthorFilesLines
2023-11-01Add support for adjusting match options of post hoc prerequisitesBoris Kolpackov1-0/+6
2023-10-26WIP: rename match_rule() to match_rule_impl()Boris Kolpackov1-2/+2
2023-10-26WIP: add match_extra data member and rule::rematch()Boris Kolpackov1-0/+7
2023-10-26Add inject_fsdir_direct(), fsdir_rule::perform_clean_direct() functionsBoris Kolpackov1-0/+3
2023-09-20Fix issue with fallback rule priority in dist moduleBoris Kolpackov1-2/+11
While at it, also remove workarounds for the same issue in the config and test modules.
2023-05-29Explicit group: pattern membersBoris Kolpackov1-1/+4
2023-05-29Explicit group: static membersBoris Kolpackov1-1/+13
2022-11-23Take into account ad hoc recipes in rule::sub_match() (fixed GH issue #227)Boris Kolpackov1-5/+7
2022-06-28Add support for rule-specific import phase 2Boris Kolpackov1-0/+15
For example: import! [metadata, rule_hint=cxx.link] lib = libhello%lib{hello}
2022-04-20Replace match_extra::buffer with more general data storage facilityBoris Kolpackov1-3/+3
2022-04-06Add support for rule hintsBoris Kolpackov1-10/+40
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-3/+12
2021-12-02Automatically register pattern rules for dist meta-operationBoris Kolpackov1-0/+5
We need to do this in order to inject additional pattern prerequisites which may "pull" additional sources into the distribution.
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov1-2/+9
2021-06-09Fix cxx pattern rule testBoris Kolpackov1-1/+2
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov1-9/+4
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-9/+85
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-16/+12
2021-06-08Only pass target to recipe_text() if recipe is not sharedBoris Kolpackov1-1/+5
2020-12-03Add match_rule() in addition to match_recipe()Boris Kolpackov1-1/+3
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov1-1/+2
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+16
2020-10-20Add operation callback for adhoc rule match and applyBoris Kolpackov1-13/+12
2020-07-14Fix Clang warningBoris Kolpackov1-0/+2
2020-07-13Add ability to extend rule interface in source-compatible mannerBoris Kolpackov1-8/+36
2020-06-09Factor ad hoc C++ and Buildscript rules into separate filesBoris Kolpackov1-105/+0
2020-06-08Adjust rule_match name for ad hoc recipesBoris Kolpackov1-3/+9
2020-06-05Add ability to split ad hoc C++ recipe into global and local fragmentsBoris Kolpackov1-1/+4
Specifically, now we can write: {{ c++ 1 -- #include <map> -- recipe apply (action, target&) const override { ... } }}
2020-06-05Add ability to specify ad hoc recipe actionsBoris Kolpackov1-7/+15
We are reusing the buildspec syntax for that.
2020-06-03Allow process path values and targets as buildscript program namesKaren Arutyunov1-3/+3
Also deduce the recipe name.
2020-06-03Add versioning for ad hoc C++ recipesBoris Kolpackov1-8/+11
This will allow us to deal with backward-incompatible changes to cxx_rule interface and semantics.
2020-06-03Factor implementation-specific ad hoc recipe parsing to adhoc_*_ruleBoris Kolpackov1-8/+24
2020-05-29Move low-verbosity command name from adhoc_script_rule to scriptBoris Kolpackov1-6/+3
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-1/+141
2020-04-30Factor recipe to separate header/source filesBoris Kolpackov1-0/+1
2020-04-27Make rule non-copyableBoris Kolpackov1-0/+5
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-10-29Add forward declaration header for build state typesBoris Kolpackov1-0/+1
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+107
generated by cgit v1.1 at 2024-11-11 06:07:54 +0000