aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/adhoc-rule-buildscript.cxx
AgeCommit message (Collapse)AuthorFilesLines
2022-04-07Rename {match,execute}() to *_sync(), add *_complete()Boris Kolpackov1-4/+2
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-03-15Don't consider mtime of failed to unmatch prerequisite in ad hoc recipeBoris Kolpackov1-3/+5
2022-03-09Parallel implementation of update_during_match_prerequisites()Boris Kolpackov1-2/+3
2022-03-08Improve performance of update during match for multiple targetsBoris Kolpackov1-9/+5
2022-03-08Add update=execute special value for cases where it's not defaultBoris Kolpackov1-1/+1
2022-03-07Add support for update=unmatch|match to ad hoc recipesBoris Kolpackov1-11/+144
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-8/+8
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-16Invent quoting modes for to_stream(name)Karen Arutyunov1-1/+1
2022-01-18Add dynamic prerequisites to $< unless --adhoc is specifiedBoris Kolpackov1-0/+2
Also add a few tests for depdb-dyndep.
2022-01-06Add depdb-dyndep --update-{include,exclude} optionsBoris Kolpackov1-135/+155
These options specify prerequisite targets/patterns to include/exclude (from the static prerequisite set) for update during match as part of dynamic dependency extraction (those excluded will be updated during execute). For example: depdb dyndep ... --update-exclude libue{hello-meta} ... depdb dyndep ... --update-exclude libue{*} ... depdb dyndep ... --update-include $moc --update-include hxx{*} ... The order in which these options are specified is significant with the first target/pattern that matches determining the result. If only the --update-include options are specified, then only the explicitly included prerequisites will be updated. Otherwise, all prerequisites that are not explicitly excluded will be updated. If none of these options is specified, then all the static prerequisites are updated during match. Note also that these options do not apply to ad hoc prerequisites which are always updated during match.
2021-12-14Clean .t file in ad hoc recipeBoris Kolpackov1-3/+18
2021-12-06Recognize absolute Windows paths in make parserBoris Kolpackov1-2/+1
2021-12-06Redo make_parser interface to return path, handle invalid_path exceptionBoris Kolpackov1-2/+2
2021-12-03Get rid of unused lambda capturesBoris Kolpackov1-1/+1
2021-12-03Add depdb-dyndep --drop-cycles optionBoris Kolpackov1-33/+23
2021-11-30Get rid of unused lambda capturesBoris Kolpackov1-4/+4
2021-11-30Add support for dynamic dependencies as byproduct of script bodyBoris Kolpackov1-64/+509
Specifically, the `depdb dyndep` builtin now has the --byproduct option (which must come first). In this mode only the --file input is supported. For example: obje{hello.o}: cxx{hello} {{ o = $path($>) t = $(o).t depdb dyndep --byproduct --what=header --default-type=h --file $t diag c++ ($<[0]) $cxx.path $cxx.poptions $cc.poptions $cc.coptions $cxx.coptions $cxx.mode -o $o -MD -MF $t -c $path($<[0]) }} Naturally, this mode does not support dynamic auto-generated prerequisites. If present, such prerequisites must be specified statically in the buildfile. Note also that the --default-prereq-type option has been rename to --default-type.
2021-11-28Avoid unnecessary work in depdb::close() if using static check_mtime()Boris Kolpackov1-1/+1
2021-11-28Generalize depdb::touch functionality to support custom timestampBoris Kolpackov1-1/+1
2021-11-23Add support for dynamic dependencies in ad hoc Buildscript recipesBoris Kolpackov1-215/+528
Specifically, add the new `depdb dyndep` builtin that can be used to extract dynamic dependencies from a program run or a file. For example: obje{hello.o}: cxx{hello} {{ s = $path($<[0]) depdb dyndep $cxx.poptions $cc.poptions --what=header --default-prereq-type=h -- $cxx.path $cxx.poptions $cc.poptions $cxx.mode -M -MG $s diag c++ ($<[0]) o = $path($>) $cxx.path $cxx.poptions $cc.poptions $cc.coptions $cxx.coptions $cxx.mode -o $o -c $s }} Currently only the `make` dependency format is supported.
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov1-2/+25
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov1-7/+3
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-7/+15
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-26/+16
2021-06-08Only pass target to recipe_text() if recipe is not sharedBoris Kolpackov1-3/+7
2021-05-12Keep phase locked while working own queueBoris Kolpackov1-3/+1
2021-04-20Detect environment changes in ad hoc recipesBoris Kolpackov1-13/+25
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov1-65/+60
2020-11-19Remove target files on ad hoc rule update buildscript errorKaren Arutyunov1-1/+18
2020-11-06Add support for test timeoutsKaren Arutyunov1-5/+20
2020-11-02Set executable bit for ad hoc buildscript rule executable target on POSIXKaren Arutyunov1-0/+22
2020-10-20Add operation callback for adhoc rule match and applyBoris Kolpackov1-2/+3
2020-07-12Rename rule-adhoc-* to adhoc-rule-*Boris Kolpackov1-0/+603