| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2021-09-20 | Add support for disabling clean through target-prerequisite relationship | Boris Kolpackov | 1 | -2/+2 | |
| Our current semantics is to clean any prerequisites that are in the same project (root scope) as the target and it may seem more natural to rather only clean prerequisites that are in the same base scope. While it's often true for simple projects, in more complex cases it's not unusual to have common intermediate build results (object files, utility libraries, etc) reside in the parent and/or sibling directories. With such arrangements, cleaning only in base (even from the project root) may leave such intermediate build results laying around (since there is no reason to list them as prerequisites of any directory aliases). So we clean in the root scope by default but now any target-prerequisite relationship can be marked not to trigger a clean with the clean=false prerequisite-specific value. | |||||
| 2021-06-08 | Redo fallback reverse operation machinery in ad hoc recipes | Boris Kolpackov | 1 | -2/+1 | |
| 2020-10-20 | Add operation callback for adhoc rule match and apply | Boris Kolpackov | 1 | -2/+13 | |
| 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 | -4/+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-10-29 | Add forward declaration header for build state types | Boris Kolpackov | 1 | -13/+1 | |
| 2019-10-23 | Un-tune scheduler when building build system modules | Boris Kolpackov | 1 | -2/+5 | |
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -8/+10 | |
| 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-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+361 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |