Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2021-12-16 | Verify targets that alias same path are read-only | Boris Kolpackov | 1 | -1/+113 | |
2021-12-16 | Pass context to (meta-)operation hooks | Boris Kolpackov | 1 | -1/+1 | |
2021-10-16 | Improve info meta-operation not to print trailing spaces | Boris Kolpackov | 1 | -8/+22 | |
2021-09-16 | Fix over-tight assumption in standard operation match() | Boris Kolpackov | 1 | -0/+1 | |
2021-08-02 | Print list of bootstrapped modules in info meta-operation | Boris Kolpackov | 1 | -1/+10 | |
2021-03-19 | Redo entering of src directories into scope_map | Boris Kolpackov | 1 | -2/+4 | |
2020-10-20 | Add operation callback for adhoc rule match and apply | Boris Kolpackov | 1 | -0/+6 | |
2020-08-25 | Fix bug in interaction of unmatch logic with target groups | Boris Kolpackov | 1 | -0/+15 | |
2020-07-12 | Cache subprojects variable value in scope::root_extra | Boris Kolpackov | 1 | -1/+1 | |
2020-07-09 | Add support for ad hoc importation | Boris Kolpackov | 1 | -1/+1 | |
2020-07-02 | Cache project name in root_extra | Boris Kolpackov | 1 | -1/+1 | |
2020-05-27 | Suppress skip count diagnostics if no progress was requested | Boris Kolpackov | 1 | -2/+5 | |
2020-05-27 | Amalgamation cutoff support | Boris Kolpackov | 1 | -1/+1 | |
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope. | |||||
2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
2019-11-04 | Add support for configuration exporting and importing | Boris Kolpackov | 1 | -7/+7 | |
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 | Un-tune scheduler when building build system modules | Boris Kolpackov | 1 | -77/+82 | |
2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -47/+56 | |
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 | -0/+1 | |
2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+617 | |