aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/config/init.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-01-28Use scope::var_pool()Boris Kolpackov1-2/+2
2020-01-28Use scope::insert_rule()Boris Kolpackov1-14/+8
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-1/+1
2019-11-13Implement config.config.persist logicBoris Kolpackov1-1/+29
Note that the inherited value part is documented but is not yet fully implemented.
2019-11-12Infra work for customizable config var persistence (config.config.persist)Boris Kolpackov1-7/+28
2019-11-12Rename config.{import,export} to config.config.{load,save}Boris Kolpackov1-15/+20
Also rename the $config.export() function to $config.save().
2019-11-12Rename config.module to config.config.moduleBoris Kolpackov1-10/+10
The old name was an accidental land-grab.
2019-11-11Change default for unused config.import.* variables from drop to keepBoris Kolpackov1-7/+7
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-7/+5
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-1/+4
2019-11-04Add support for ~host special configuration name in config.importBoris Kolpackov1-5/+37
This is the "default host configuration" that corresponds to how the build system itself was built. For example: $ b create: tools/,cc config.import=~host
2019-11-04Add $config.export() functionBoris Kolpackov1-6/+25
This is similar to the config.export variable functionality except it can be called from within buildfiles. Note that this function can only be used during configure unless the config module creation was forced for other meta-operations with config.module=true in bootstrap.build.
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-30/+78
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-5/+5
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-24Move in build system module to separate libraryBoris Kolpackov1-4/+10
2019-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+159