aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/build/script/parser.hxx
AgeCommit message (Collapse)AuthorFilesLines
2022-06-28Add support for querying out-qualified target-specific variablesBoris Kolpackov1-1/+1
2022-01-06Add depdb-dyndep --update-{include,exclude} optionsBoris Kolpackov1-9/+8
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-03Add depdb-dyndep --drop-cycles optionBoris Kolpackov1-0/+1
2021-11-30Add support for dynamic dependencies as byproduct of script bodyBoris Kolpackov1-5/+55
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-23Add support for dynamic dependencies in ad hoc Buildscript recipesBoris Kolpackov1-9/+70
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-10-14Disable re-parse of sole expansions in BuildscriptBoris Kolpackov1-1/+1
2021-10-14Pass along parse_names_result during script command parsingBoris Kolpackov1-3/+2
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov1-4/+8
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov1-3/+13
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-2/+2
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-08Only pass target to recipe_text() if recipe is not sharedBoris Kolpackov1-2/+3
2021-04-21Add buildscript depdb builtin 'env' commandKaren Arutyunov1-5/+8
2020-12-08In update ad hoc recipe buildscripts allow non-pure function calls only in ↵Karen Arutyunov1-0/+19
depdeb preamble
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov1-6/+35
2020-06-18Add env script pseudo-builtinKaren Arutyunov1-3/+6
Also disable C++ recipe tests when cross-testing.
2020-06-08Fix crashing when special builtin appears inside if condition or branchKaren Arutyunov1-0/+10
2020-06-05Add depdb buildscript builtinKaren Arutyunov1-8/+26
2020-06-04Properly handle diag directive in build script parserKaren Arutyunov1-13/+48
2020-06-03Allow process path values and targets as buildscript program namesKaren Arutyunov1-2/+45
Also deduce the recipe name.
2020-05-29Move low-verbosity command name from adhoc_script_rule to scriptBoris Kolpackov1-1/+2
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-0/+96