build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2019-11-13	Implement config.config.persist logic	Boris Kolpackov	1	-76/+153
	Note that the inherited value part is documented but is not yet fully implemented.
2019-11-12	Infra work for customizable config var persistence (config.config.persist)	Boris Kolpackov	1	-33/+41

2019-11-12	Rename config.{import,export} to config.config.{load,save}	Boris Kolpackov	1	-25/+24
	Also rename the $config.export() function to $config.save().
2019-11-11	Change default for unused config.import.* variables from drop to keep	Boris Kolpackov	1	-16/+70

2019-11-07	Initial work on path_name use for `-` to stdin/stdout translation	Boris Kolpackov	1	-16/+17

2019-11-04	Add $config.export() function	Boris Kolpackov	1	-30/+48
	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-04	Add support for configuration exporting and importing	Boris Kolpackov	1	-99/+165
	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-10-23	Expand comment	Boris Kolpackov	1	-2/+2

2019-08-23	Introduce notion of build context	Boris Kolpackov	1	-95/+107
	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-05	Move config, dist, test, and install modules into library	Karen Arutyunov	1	-0/+997