aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/version/init.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-08-17Add mvfile() filesystem utility functionBoris Kolpackov1-19/+7
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-2/+4
2020-07-02Cache project name in root_extraBoris Kolpackov1-8/+8
2020-04-27Require explicit variable type in scope::{assign,append}()Boris Kolpackov1-4/+5
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-8/+4
2020-03-25Diagnose unnamed project in version moduleBoris Kolpackov1-3/+6
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov1-10/+10
2020-01-28Use scope::var_pool()Boris Kolpackov1-1/+1
2020-01-28Use scope::insert_rule()Boris Kolpackov1-11/+7
2020-01-27Improve module loading APIBoris Kolpackov1-5/+3
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-3/+3
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-0/+3
The new config.export variable specifies the alternative file to write the configuration to as part of the configure meta-operation. For example: $ b configure: proj/ config.export=proj-config.build The config.export value "applies" only to the projects on whose root scope it is specified or if it is a global override (the latter is a bit iffy but we allow it, for example, to dump everything to stdout). This means that in order to save a subproject's configuration we will have to use a scope-specific override (since the default will apply to the outermost amalgamation). For example: $ b configure: subproj/ subproj/config.export=.../subproj-config.build This could be somewhat unnatural but then it will be the amalgamation whose configuration we normally want to export. The new config.import variable specifies additional configuration files to be loaded after the project's default config.build, if any. For example: $ b create: cfg/,cc config.import=my-config.build Similar to config.export, the config.import value "applies" only to the project on whose root scope it is specified or if it is a global override. This allows the use of the standard override "positioning" machinery (i.e., where the override applies) to decide where the extra configuration files are loaded. The resulting semantics is quite natural and consistent with command line variable overrides, for example: $ b config.import=.../config.build # outermost amalgamation $ b ./config.import=.../config.build # this project $ b !config.import=.../config.build # every project Both config.export and config.import recognize the special `-` file name as an instruction to write/read to/from stdout/stdin, respectively. For example: $ b configure: src-prj/ config.export=- | b configure: dst-prj/ config.import=-
2019-08-23Introduce notion of build contextBoris Kolpackov1-7/+12
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-08-21Cleanup context.hxx and its usageBoris Kolpackov1-1/+0
2019-08-01Move version build system module to separate libraryKaren Arutyunov1-0/+407