| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2020-06-02 | Add process_path_ex with program stable name and checksum | Boris Kolpackov | 1 | -0/+2 | |
| 2020-06-01 | Extend target metadata to include variable prefix, stable name | Boris Kolpackov | 1 | -3/+25 | |
| 2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -5/+14 | |
| 2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -0/+5 | |
| 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-13 | Cleanup and make config/utility.?xx part of build system core | Boris Kolpackov | 1 | -12/+0 | |
| 2020-02-11 | Add match_only flag to context | Boris Kolpackov | 1 | -0/+5 | |
| 2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
| 2019-10-29 | Add forward declaration header for build state types | Boris Kolpackov | 1 | -20/+1 | |
| 2019-10-25 | Fix inconsistent loaded_modules_lock declaration | Boris Kolpackov | 1 | -1/+1 | |
| 2019-10-25 | Expand context comment | Boris Kolpackov | 1 | -2/+13 | |
| 2019-10-23 | Un-tune scheduler when building build system modules | Boris Kolpackov | 1 | -0/+3 | |
| 2019-10-22 | Implement loaded_modules state locking | Boris Kolpackov | 1 | -1/+13 | |
| 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 | -4/+9 | |
| 2019-10-22 | Move global mutex shards to context | Boris Kolpackov | 1 | -0/+14 | |
| 2019-08-30 | Cutoff diagnostics stack when switching to nested context | Boris Kolpackov | 1 | -2/+11 | |
| 2019-08-27 | Propagate global var overrides to module build context | Boris Kolpackov | 1 | -0/+1 | |
| 2019-08-27 | Redo module context pointer | Boris Kolpackov | 1 | -6/+6 | |
| 2019-08-26 | Implement auto-import of development build2 build | Boris Kolpackov | 1 | -1/+2 | |
| 2019-08-26 | Implement updating build system modules | Boris Kolpackov | 1 | -2/+21 | |
| 2019-08-26 | Make target types project-wide | Boris Kolpackov | 1 | -5/+7 | |
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -257/+345 | |
| 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 | -99/+5 | |
| 2019-08-19 | Minor cleanups | Boris Kolpackov | 1 | -124/+104 | |
| 2019-08-01 | Fix linkage failure due to inline functions defined in ↵ | Karen Arutyunov | 1 | -1/+1 | |
| libbuild2/algorithm.ixx and referred from libbuild2/target.txx | |||||
| 2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+572 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |