aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/rule.cxx
AgeCommit message (Collapse)AuthorFilesLines
2023-05-09Add --load-only option in addition to --match-onlyBoris Kolpackov1-1/+17
This option has the effect of loading all the subdirectory buildfiles that are not explicitly included.
2023-05-09Add support for dumping build system state in JSON format (GH issue #182)Boris Kolpackov1-1/+1
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-11-23Take into account ad hoc recipes in rule::sub_match() (fixed GH issue #227)Boris Kolpackov1-0/+22
2022-11-16Initial low verbosity diagnostics reworkBoris Kolpackov1-1/+1
2022-09-07Fix fsdir{} handling corner cases in ad hoc buildscript recipes/rulesdist-remapBoris Kolpackov1-1/+1
2022-06-28Add support for rule-specific import phase 2Boris Kolpackov1-0/+8
For example: import! [metadata, rule_hint=cxx.link] lib = libhello%lib{hello}
2022-04-06Add support for rule hintsBoris Kolpackov1-7/+22
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-02-09Don't use fallback file_rule to clean real targetsBoris Kolpackov1-1/+4
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-4/+23
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-4/+3
2020-12-03Add match_rule() in addition to match_recipe()Boris Kolpackov1-0/+1
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+7
2020-10-20Add operation callback for adhoc rule match and applyBoris Kolpackov1-3/+4
2020-07-17Fix race in path/mtime assignment and file_rule::match()Boris Kolpackov1-0/+3
2020-07-17Add optimized derive_path_with_extension(), use in file_ruleBoris Kolpackov1-3/+5
2020-07-13Add ability to extend rule interface in source-compatible mannerBoris Kolpackov1-0/+14
2020-06-09Move recipe build directory to build/build/recipes/Boris Kolpackov1-6/+14
Our new scheme is to have any "out" content in a subdirectory called build/ (build/build/ for the build system core, build/<module>/build/ for modules). This way we can ignore them in .gitignore with a generic entry.
2020-06-09Factor ad hoc C++ and Buildscript rules into separate filesBoris Kolpackov1-1225/+0
2020-06-08Various minor fixesKaren Arutyunov1-2/+2
2020-06-08Hash ad hoc prerequsites for ad hoc recipe change detectionBoris Kolpackov1-59/+139
2020-06-08Adjust rule_match name for ad hoc recipesBoris Kolpackov1-1/+4
2020-06-08Fix handling of inner/outer operations in ad hoc recipes machineryBoris Kolpackov1-3/+15
2020-06-05Add depdb buildscript builtinKaren Arutyunov1-101/+196
2020-06-05Add ability to split ad hoc C++ recipe into global and local fragmentsBoris Kolpackov1-15/+101
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-17/+17
We are reusing the buildspec syntax for that.
2020-06-04Properly handle diag directive in build script parserKaren Arutyunov1-35/+56
2020-06-03Allow process path values and targets as buildscript program namesKaren Arutyunov1-13/+8
Also deduce the recipe name.
2020-06-03Add versioning for ad hoc C++ recipesBoris Kolpackov1-9/+26
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-0/+42
2020-06-02Hash checksum metadata of exe prerequisites in ad hoc script ruleBoris Kolpackov1-16/+56
2020-05-29Move low-verbosity command name from adhoc_script_rule to scriptBoris Kolpackov1-6/+10
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-5/+887
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-18Add couple of sanity checksBoris Kolpackov1-1/+1
2019-08-23Introduce notion of build contextBoris Kolpackov1-2/+2
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-07-01Split build system into library and driverBoris Kolpackov1-0/+309
generated by cgit v1.1 at 2024-11-15 20:23:11 +0000