build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2022-11-18	Complete low verbosity diagnostics rework	Boris Kolpackov	1	-1/+1

2022-11-09	Use diag_buffer in script	Karen Arutyunov	1	-2/+2

2022-10-18	Invent diag preamble for buildscript	Karen Arutyunov	1	-25/+59

2022-10-13	Add support for 'for' loop second (... \| for x) and third (for x <...) forms ↵	Karen Arutyunov	1	-2/+23
	in script
2022-10-10	Preparatory work for public/private variable distinction	Boris Kolpackov	1	-3/+5
	We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-28	Add support for 'while' loop in script	Karen Arutyunov	1	-14/+43

2022-02-21	Factor process-wide initialization to init_process() function	Boris Kolpackov	1	-1/+1

2022-02-10	Make few global types separately constructible/initializable	Boris Kolpackov	1	-1/+1

2021-09-24	Fortify tests against NDEBUG	Karen Arutyunov	1	-1/+3

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

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

2021-06-08	Implement ad hoc regex pattern rule support	Boris Kolpackov	1	-1/+1
	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	-1/+1

2021-03-18	Add noop mode to file cache, add --file-cache option to select	Boris Kolpackov	1	-1/+1

2021-03-16	Define intermediate build results file cache interface	Boris Kolpackov	1	-1/+3

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

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

2020-06-03	Allow process path values and targets as buildscript program names	Karen Arutyunov	1	-2/+7
	Also deduce the recipe name.
2020-06-01	Fix buildscript unit test to compile	Boris Kolpackov	1	-1/+1

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