| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2024-04-02 | Detect and diagnose attempt to create new target in src directory | Boris Kolpackov | 1 | -0/+27 | |
| GitHub issue #277. | |||||
| 2023-12-03 | Search in src for existing prerequisites with unspecified out | Boris Kolpackov | 1 | -4/+28 | |
| 2022-10-20 | Don't create targets for non-existent source files | Boris Kolpackov | 1 | -14/+12 | |
| 2022-10-20 | Diagnose incorrect output directory specification | Boris Kolpackov | 1 | -10/+36 | |
| 2022-04-19 | Skip find() inside target_set::insert*() if target is unlikely to be there | Boris Kolpackov | 1 | -3/+12 | |
| 2022-03-31 | Get rid of unnecessary dynamic_cast call | Boris Kolpackov | 1 | -3/+5 | |
| 2021-02-08 | Enter scope src directories into scope map | Boris Kolpackov | 1 | -1/+1 | |
| 2020-12-14 | Fix bug in create_new_target_locked() | Karen Arutyunov | 1 | -2/+9 | |
| 2020-12-11 | Add search_locked() versions of search() functions | Boris Kolpackov | 1 | -0/+40 | |
| 2020-09-24 | Give hints for common causes of "no rule to update ..." error | Boris Kolpackov | 1 | -4/+8 | |
| 2020-07-17 | Fix race in path/mtime assignment and file_rule::match() | Boris Kolpackov | 1 | -2/+1 | |
| 2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -1/+1 | |
| 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-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -12/+13 | |
| 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 | -1/+0 | |
| 2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+244 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |