aboutsummaryrefslogtreecommitdiff
path: root/build2/scope.hxx
AgeCommit message (Collapse)AuthorFilesLines
2019-01-16Update copyright yearKaren Arutyunov1-1/+1
2019-01-14Diagnose target names with multiple trailing slashes as invalidBoris Kolpackov1-5/+5
2018-11-13Minor terminology tweaks (model -> build state)Boris Kolpackov1-1/+1
2018-11-09Add support for relative to base scope command line variable overridesBoris Kolpackov1-1/+2
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-08Fix bug in override logic for command line variable with project visibilityBoris Kolpackov1-0/+6
2018-11-01Add support for rule-specific variables, use to fix cc.type data raceBoris Kolpackov1-1/+2
2018-08-07Add support for default extension specification, trailing dot escapingBoris Kolpackov1-4/+4
For example: cxx{*}: extension = cxx cxx{foo} # foo.cxx cxx{foo.test} # foo.test (probably what we want...) cxx{foo.test...} # foo.test.cxx (... is this) cxx{foo..} # foo. cxx{foo....} # foo.. cxx{foo.....} # error (must come in escape pair)
2018-05-19Update copyright yearKaren Arutyunov1-1/+1
2018-05-16Fix uncaught invalid_path exceptionKaren Arutyunov1-1/+1
2018-04-26Implement forwarded configurations and backlinkingBoris Kolpackov1-5/+1
2017-12-03Allow typification of variables and values across load generationsBoris Kolpackov1-1/+1
The original semantics turned out to be too restrictive. For example, the user may have specified the config.c variable on the command line that is only used by an imported project that is loaded in a subsequent generation. We are also relaxing it for values since conceptually the two feel the same. For a value the (hypothetical) example is a "common" variable set in a project root that is only queried in a subdirectory in a subsequent generation.
2017-11-30Implement support for scope operation callbacksBoris Kolpackov1-1/+32
An entity (module, core) can register a function that will be called when an action is executed on the dir{} target that corresponds to the scope. The pre callback is called just before the recipe and the post -- immediately after.
2017-10-03Adapt to modularization of libbutlKaren Arutyunov1-1/+1
2017-08-05Minor changesBoris Kolpackov1-0/+5
2017-05-01Add hxx extension for headersKaren Arutyunov1-0/+375