build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2022-12-02	Fail if scope or target qualification in variable expansion is unknown	Boris Kolpackov	1	-0/+19
	There are three options here: we can "fall through" to an outer scope (there is always the global scope backstop; this is the old semantics, sort of), we can return NULL straight away, or we can fail. It feels like in most cases unknown scope or target is a mistake and doing anything other than failing is just making things harder to debug.
2021-06-08	Get rid of special *{} wildcard target type notation in target type/patterns	Boris Kolpackov	1	-1/+1
	Explicit target{} should be used instead. Also, in this context, absent target type is now treated as file{} rather than target{}, for consistency with all other cases.
2021-05-28	Add support for regex-based target type/pattern specific variables	Boris Kolpackov	1	-0/+127
	This is in addition to the already supported path-based target type/pattern specific variables. For example: hxx{}: x = y # path-based hxx{~/./}: x = y # regex-based
2020-02-07	Drop copyright notice from source code	Karen Arutyunov	2	-2/+0

2019-01-16	Update copyright year	Karen Arutyunov	2	-2/+2

2018-11-21	Add support for target and prerequisite specific variable blocks	Boris Kolpackov	2	-0/+63
	For example, now instead of: lib{foo}: cxx.loptions += -static lib{foo}: cxx.libs += -lpthread We can write: lib{foo}: { cxx.loptions += -static cxx.libs += -lpthread } The same works for prerequisites as well as target type/patterns. For example: exe{*.test}: { test = true install = false }