aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/adhoc-rule-buildscript.cxx
AgeCommit message (Collapse)AuthorFilesLines
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