build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2021-11-23	Add support for dynamic dependencies in ad hoc Buildscript recipes	Boris Kolpackov	1	-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-14	Disable re-parse of sole expansions in Buildscript	Boris Kolpackov	1	-1/+1

2021-10-14	Pass along parse_names_result during script command parsing	Boris Kolpackov	1	-3/+2

2021-08-04	Take into account file-base'ness in ad hoc buildscript recipes	Boris Kolpackov	1	-4/+8

2021-06-08	Redo low verbosity diagnostic deduction to use scope instead of target	Boris Kolpackov	1	-3/+13

2021-06-08	Implement ad hoc regex pattern rule support	Boris Kolpackov	1	-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-08	Only pass target to recipe_text() if recipe is not shared	Boris Kolpackov	1	-2/+3

2021-04-21	Add buildscript depdb builtin 'env' command	Karen Arutyunov	1	-5/+8

2020-12-08	In update ad hoc recipe buildscripts allow non-pure function calls only in ↵	Karen Arutyunov	1	-0/+19
	depdeb preamble
2020-12-02	Add support for buildscript depdb preamble	Karen Arutyunov	1	-6/+35

2020-06-18	Add env script pseudo-builtin	Karen Arutyunov	1	-3/+6
	Also disable C++ recipe tests when cross-testing.
2020-06-08	Fix crashing when special builtin appears inside if condition or branch	Karen Arutyunov	1	-0/+10

2020-06-05	Add depdb buildscript builtin	Karen Arutyunov	1	-8/+26

2020-06-04	Properly handle diag directive in build script parser	Karen Arutyunov	1	-13/+48

2020-06-03	Allow process path values and targets as buildscript program names	Karen Arutyunov	1	-2/+45
	Also deduce the recipe name.
2020-05-29	Move low-verbosity command name from adhoc_script_rule to script	Boris Kolpackov	1	-1/+2

2020-05-27	Initial support for ad hoc recipes (still work in progress)	Boris Kolpackov	1	-0/+96