aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/build
AgeCommit message (Collapse)AuthorFilesLines
2021-12-03Add depdb-dyndep --drop-cycles optionBoris Kolpackov6-27/+84
2021-11-30Add support for dynamic dependencies as byproduct of script bodyBoris Kolpackov7-159/+368
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 Kolpackov10-94/+2501
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 Kolpackov3-3/+36
2021-10-14Pass along parse_names_result during script command parsingBoris Kolpackov2-12/+11
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov3-3/+3
2021-09-24Fortify tests against NDEBUGKaren Arutyunov2-2/+6
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov3-7/+17
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov3-22/+26
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov3-4/+6
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 Kolpackov3-12/+19
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 Arutyunov2-6/+36
2021-04-20Detect environment changes in ad hoc recipesBoris Kolpackov1-1/+1
2021-03-18Add noop mode to file cache, add --file-cache option to selectBoris Kolpackov1-1/+1
2021-03-16Define intermediate build results file cache interfaceBoris Kolpackov1-1/+3
2020-12-11Prefix pseudo-builtin diagnostincs messages with their namesKaren Arutyunov1-2/+3
2020-12-08In update ad hoc recipe buildscripts allow non-pure function calls only in ↵Karen Arutyunov3-2/+100
depdeb preamble
2020-12-08Add support for config.test.runnerKaren Arutyunov1-0/+10
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov8-126/+555
2020-11-06Add support for test timeoutsKaren Arutyunov2-4/+50
2020-06-18Add env script pseudo-builtinKaren Arutyunov3-4/+47
Also disable C++ recipe tests when cross-testing.
2020-06-18Fix untracked variable check in buildscript parserKaren Arutyunov1-1/+1
2020-06-10Handle special variable names in base lexer via mode dataBoris Kolpackov2-33/+9
2020-06-08Fix crashing when special builtin appears inside if condition or branchKaren Arutyunov2-1/+33
2020-06-08Fix crashing for buildscript diag line using non-local variableKaren Arutyunov1-11/+35
2020-06-08Add note on why not using rule-specific variables for ad hoc recipesBoris Kolpackov1-2/+10
2020-06-05Add depdb buildscript builtinKaren Arutyunov5-53/+163
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 Arutyunov5-58/+273
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 Arutyunov6-23/+471
Also deduce the recipe name.
2020-06-01Fix buildscript unit test to compileBoris Kolpackov1-1/+1
2020-05-29Move low-verbosity command name from adhoc_script_rule to scriptBoris Kolpackov3-2/+11
2020-05-27Add support for value subscript after expansionsBoris Kolpackov1-8/+7
Value subscript is only recognized in evaluation contexts (due to ambiguity with wildcard patterns; consider: $x[123].txt) and should be unseparated from the previous token. For example: x = ($y[1]) x = (($f ? $y : $z)[1]) x = ($identity($y)[$z])
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov30-0/+3937
generated by cgit v1.1 at 2024-11-08 23:57:50 +0000