| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2019-11-04 | Add support for configuration exporting and importing | Boris Kolpackov | 1 | -1/+1 | |
| 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-22 | Implement loaded_modules state locking | Boris Kolpackov | 1 | -1/+3 | |
| This would be necessary if someone runs two parallel top-level contexts. | |||||
| 2019-10-22 | Rename global_mutex_shards to global_mutexes | Boris Kolpackov | 1 | -2/+2 | |
| 2019-10-22 | Move global mutex shards to context | Boris Kolpackov | 1 | -0/+2 | |
| 2019-08-28 | Redo build_installed without requiring linking whole archive | Boris Kolpackov | 1 | -1/+3 | |
| 2019-08-27 | Propagate global var overrides to module build context | Boris Kolpackov | 1 | -0/+7 | |
| 2019-08-27 | Redo module context pointer | Boris Kolpackov | 1 | -3/+5 | |
| 2019-08-27 | Don't set import.build2 variable in cross-compiled build2 | Karen Arutyunov | 1 | -1/+1 | |
| 2019-08-26 | Implement auto-import of development build2 build | Boris Kolpackov | 1 | -0/+10 | |
| 2019-08-26 | Implement updating build system modules | Boris Kolpackov | 1 | -3/+9 | |
| 2019-08-26 | Make target types project-wide | Boris Kolpackov | 1 | -5/+8 | |
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -414/+396 | |
| 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-21 | Cleanup context.hxx and its usage | Boris Kolpackov | 1 | -183/+32 | |
| 2019-08-21 | Implement dynamic loading of build system modules | Boris Kolpackov | 1 | -4/+1 | |
| 2019-08-20 | Add build.version.interface | Boris Kolpackov | 1 | -0/+11 | |
| This build system interface version should be embedded into build system modules as load_suffix. | |||||
| 2019-08-19 | Minor cleanups | Boris Kolpackov | 1 | -48/+50 | |
| 2019-08-07 | Distinguish between internal/external wait deactivation in scheduler | Boris Kolpackov | 1 | -4/+4 | |
| This turns out to be necessary for the deadlock detection to work properly. | |||||
| 2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+1026 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |