aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/scope.cxx
AgeCommit message (Collapse)AuthorFilesLines
2021-05-28Tie loose ends in target type/pattern-specific matchingBoris Kolpackov1-13/+22
2021-05-28Clean default target type extension logicBoris Kolpackov1-0/+38
2021-05-28Make notion of name pattern explicit, fix various related loose endsBoris Kolpackov1-23/+16
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-49/+69
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-13/+46
2020-11-12Assign fixed extensions to wasm{} and pdb{} target typesBoris Kolpackov1-0/+9
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-0/+18
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-9/+43
Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)"
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-2/+2
2020-03-19Tweak lookup_config() semantics some moreBoris Kolpackov1-7/+9
2020-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov1-29/+29
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases.
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-10-22Move global mutex shards to contextBoris Kolpackov1-4/+6
2019-08-26Fix bug in scope::find_target_key()Boris Kolpackov1-1/+8
2019-08-26Suppress gcc's 'control reaches end of non-void function' warningKaren Arutyunov1-1/+1
2019-08-26Factor target name processing code from parser to scopeBoris Kolpackov1-0/+59
2019-08-26Make target types project-wideBoris Kolpackov1-26/+13
2019-08-23Introduce notion of build contextBoris Kolpackov1-19/+14
All non-const global state is now in class context and we can now have multiple independent builds going on at the same time.
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+911