build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2021-06-08	Redo low verbosity diagnostic deduction to use scope instead of target	Boris Kolpackov	1	-9/+4

2021-06-08	Implement ad hoc regex pattern rule support	Boris Kolpackov	1	-9/+85
	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	Redo fallback reverse operation machinery in ad hoc recipes	Boris Kolpackov	1	-16/+12

2021-06-08	Only pass target to recipe_text() if recipe is not shared	Boris Kolpackov	1	-1/+5

2020-12-03	Add match_rule() in addition to match_recipe()	Boris Kolpackov	1	-1/+3

2020-12-02	Add support for buildscript depdb preamble	Karen Arutyunov	1	-1/+2

2020-11-06	Add support for test timeouts	Karen Arutyunov	1	-0/+16

2020-10-20	Add operation callback for adhoc rule match and apply	Boris Kolpackov	1	-13/+12

2020-07-14	Fix Clang warning	Boris Kolpackov	1	-0/+2

2020-07-13	Add ability to extend rule interface in source-compatible manner	Boris Kolpackov	1	-8/+36

2020-06-09	Factor ad hoc C++ and Buildscript rules into separate files	Boris Kolpackov	1	-105/+0

2020-06-08	Adjust rule_match name for ad hoc recipes	Boris Kolpackov	1	-3/+9

2020-06-05	Add ability to split ad hoc C++ recipe into global and local fragments	Boris Kolpackov	1	-1/+4
	Specifically, now we can write: {{ c++ 1 -- #include <map> -- recipe apply (action, target&) const override { ... } }}
2020-06-05	Add ability to specify ad hoc recipe actions	Boris Kolpackov	1	-7/+15
	We are reusing the buildspec syntax for that.
2020-06-03	Allow process path values and targets as buildscript program names	Karen Arutyunov	1	-3/+3
	Also deduce the recipe name.
2020-06-03	Add versioning for ad hoc C++ recipes	Boris Kolpackov	1	-8/+11
	This will allow us to deal with backward-incompatible changes to cxx_rule interface and semantics.
2020-06-03	Factor implementation-specific ad hoc recipe parsing to adhoc_*_rule	Boris Kolpackov	1	-8/+24

2020-05-29	Move low-verbosity command name from adhoc_script_rule to script	Boris Kolpackov	1	-6/+3

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

2020-04-30	Factor recipe to separate header/source files	Boris Kolpackov	1	-0/+1

2020-04-27	Make rule non-copyable	Boris Kolpackov	1	-0/+5

2020-02-07	Drop copyright notice from source code	Karen Arutyunov	1	-1/+0

2019-10-29	Add forward declaration header for build state types	Boris Kolpackov	1	-0/+1

2019-07-01	Split build system into library and driver	Boris Kolpackov	1	-0/+107