| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2021-04-02 | Add support for propagating project environment | Boris Kolpackov | 1 | -1/+3 | |
| 2021-03-16 | Define intermediate build results file cache interface | Boris Kolpackov | 1 | -0/+1 | |
| 2021-01-13 | Make sure we don't work any existing tasks when building in module context | Boris Kolpackov | 1 | -0/+6 | |
| 2020-09-24 | Add post-boot module function | Boris Kolpackov | 1 | -3/+24 | |
| 2020-09-22 | Add ability to skip external modules during bootstrap (--no-external-modules) | Boris Kolpackov | 1 | -33/+61 | |
| 2020-09-09 | Expand notes on issues with build system modules that require bootstrap | Boris Kolpackov | 1 | -0/+6 | |
| 2020-09-08 | Get rid of warning in static build | Boris Kolpackov | 1 | -0/+2 | |
| 2020-09-08 | Allow external modules that require bootstrap | Boris Kolpackov | 1 | -13/+34 | |
| 2020-08-16 | Add ability to initialize bootstrapped modules after loading root.build | Boris Kolpackov | 1 | -9/+9 | |
| 2020-08-16 | Redo modules map as vector | Boris Kolpackov | 1 | -20/+38 | |
| 2020-06-15 | Diagnose building of module or ad hoc C++ recipe using static build system | Boris Kolpackov | 1 | -13/+29 | |
| 2020-06-10 | Fix bootstrap build | Boris Kolpackov | 1 | -0/+4 | |
| 2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -138/+180 | |
| 2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -9/+37 | |
| Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)" | |||||
| 2020-03-31 | Switch to project variable visibility by default | Boris Kolpackov | 1 | -1/+1 | |
| 2020-02-11 | Add match_only flag to context | Boris Kolpackov | 1 | -0/+1 | |
| 2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
| 2020-01-29 | Rename module_base to module, redo module boot/init argument passing | Boris Kolpackov | 1 | -3/+12 | |
| 2020-01-28 | Use scope::var_pool() | Boris Kolpackov | 1 | -2/+2 | |
| 2020-01-27 | Improve module loading API | Boris Kolpackov | 1 | -2/+38 | |
| 2019-11-07 | Use `lib` prefix on MinGW when forming build system module library name | Boris Kolpackov | 1 | -1/+3 | |
| 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-25 | Add --silent, remap verbosity 0 to 1 while building modules unless silent | Boris Kolpackov | 1 | -0/+15 | |
| Failed that, we may have long periods of seemingly nothing happening (e.g., during implicit bdep sync) while we quietly update the module, which may look like things have hung up. | |||||
| 2019-10-23 | Un-tune scheduler when building build system modules | Boris Kolpackov | 1 | -1/+15 | |
| 2019-10-22 | Handle invalid_argument when constructing build system module project name | Boris Kolpackov | 1 | -1/+9 | |
| 2019-10-22 | Implement loaded_modules state locking | Boris Kolpackov | 1 | -0/+13 | |
| This would be necessary if someone runs two parallel top-level contexts. | |||||
| 2019-10-22 | Minor fixes | Boris Kolpackov | 1 | -1/+1 | |
| 2019-10-22 | Add load_builtin_module() | Boris Kolpackov | 1 | -0/+7 | |
| 2019-10-22 | Rename global_mutex_shards to global_mutexes | Boris Kolpackov | 1 | -2/+2 | |
| 2019-10-22 | Add tracing to find_module() and import_module() | Boris Kolpackov | 1 | -1/+20 | |
| 2019-10-22 | Move global mutex shards to context | Boris Kolpackov | 1 | -2/+3 | |
| 2019-08-30 | Cutoff diagnostics stack when switching to nested context | Boris Kolpackov | 1 | -24/+36 | |
| 2019-08-28 | Move cxx build system module to separate library | Karen Arutyunov | 1 | -0/+1 | |
| 2019-08-28 | Move c build system module to separate library | Karen Arutyunov | 1 | -0/+1 | |
| 2019-08-28 | Move cc build system module to separate library | Karen Arutyunov | 1 | -0/+1 | |
| 2019-08-28 | Move bin build system module to separate library | Karen Arutyunov | 1 | -0/+1 | |
| 2019-08-27 | Propagate global var overrides to module build context | Boris Kolpackov | 1 | -6/+6 | |
| 2019-08-26 | Improve diagnostics in import_module() | Boris Kolpackov | 1 | -20/+25 | |
| 2019-08-26 | Implement updating build system modules | Boris Kolpackov | 1 | -23/+153 | |
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -2/+2 | |
| 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-23 | Disable dynamic build system module loading in bootstrap build | Boris Kolpackov | 1 | -6/+17 | |
| We don't really need it so why jump through hoops like trying to portably link -ldl, etc. | |||||
| 2019-08-21 | Implement dynamic loading of build system modules | Boris Kolpackov | 1 | -38/+269 | |
| 2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+147 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |