aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/build/script/parser.cxx
AgeCommit message (Collapse)AuthorFilesLines
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-1/+3
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-9/+15
2021-05-28Add pattern_mode::ignore and use in appropriate placesBoris Kolpackov1-3/+3
2021-05-28Make notion of name pattern explicit, fix various related loose endsBoris Kolpackov1-3/+3
2021-04-21Add buildscript depdb builtin 'env' commandKaren Arutyunov1-1/+28
2021-04-20Detect environment changes in ad hoc recipesBoris Kolpackov1-1/+1
2020-12-08In update ad hoc recipe buildscripts allow non-pure function calls only in ↵Karen Arutyunov1-2/+32
depdeb preamble
2020-12-08Add support for config.test.runnerKaren Arutyunov1-0/+10
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov1-85/+255
2020-06-18Add env script pseudo-builtinKaren Arutyunov1-1/+5
Also disable C++ recipe tests when cross-testing.
2020-06-18Fix untracked variable check in buildscript parserKaren Arutyunov1-1/+1
2020-06-08Fix crashing when special builtin appears inside if condition or branchKaren Arutyunov1-1/+23
2020-06-08Fix crashing for buildscript diag line using non-local variableKaren Arutyunov1-11/+35
2020-06-05Add depdb buildscript builtinKaren Arutyunov1-40/+116
2020-06-05Add ability to specify ad hoc recipe actionsBoris Kolpackov1-1/+1
We are reusing the buildspec syntax for that.
2020-06-04Properly handle diag directive in build script parserKaren Arutyunov1-40/+116
2020-06-03Fix $process.run() to properly handle proces_path_exKaren Arutyunov1-9/+3
2020-06-03Allow process path values and targets as buildscript program namesKaren Arutyunov1-12/+411
Also deduce the recipe name.
2020-05-29Move low-verbosity command name from adhoc_script_rule to scriptBoris Kolpackov1-1/+4
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-0/+391