build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2019-03-14	Add support for multiple variable overrides	Boris Kolpackov	1	-3/+3
	Now we can do: $ b config.cxx.coptions=-O3 config.cxx.coptions=-O0 Or even: $ b config.cxx.coptions=-O3 config.cxx.coptions+=-g
2018-11-09	Add support for relative to base scope command line variable overrides	Boris Kolpackov	1	-0/+30
	Currently, if we say: $ b dir/ ./foo=bar The scope the foo=bar is set on is relative to CWD, not dir/. While this may seem wrong at first, this is the least surprising behavior when we take into account that there can be multiple dir/'s. Sometimes, however, we do want the override directory to be treated relative to (every) target's base scope that we are building. To support this we are extending the '.' and '..' special directory names (which are still resolved relative to CWD) with '...', which means "relative to the base scope of every target in the buildspec". For example: $ b dir/ .../foo=bar Is equivalent to: $ b dir/ dir/foo=bar And: $ b liba/ libb/ .../tests/foo=bar Is equivalent to: $ b liba/ libb/ liba/tests/foo=bar libb/tests/foo=bar
2018-11-08	Make command line variable override scope syntax consistent with buildfile	Boris Kolpackov	1	-2/+2
	Before: $ b dir/:foo=bar ... After: $ b dir/foo=bar Alternatively (the buildfile syntax): $ b 'dir/ foo=bar' Note that the (rarely used) scope visibility modifier now leads to a double slash: $ b dir//foo=bar
2018-05-03	Regularize directory target/scope-specific variable assignment syntax	Boris Kolpackov	2	-2/+2

2017-02-13	Use variable_cache for target type/pattern-specific prepend/append	Boris Kolpackov	2	-22/+0

2016-12-01	Move old tests to old-tests/	Boris Kolpackov	8	-0/+439