Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2022-11-18 | Complete low verbosity diagnostics rework | Boris Kolpackov | 1 | -2/+15 | |
2022-01-06 | Factor reusable code to target_key::effective_name() | Boris Kolpackov | 1 | -0/+6 | |
2021-12-15 | Return stable imported target name from import_direct() | Boris Kolpackov | 1 | -0/+2 | |
2021-05-28 | Fix few Windows/VC compatibility issues | Boris Kolpackov | 1 | -4/+4 | |
2021-01-30 | Add std::{map, multimap} to types.hxx | Boris Kolpackov | 1 | -1/+0 | |
Seeing that std::map is becoming a common Buildfile variable type. | |||||
2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -2/+10 | |
2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -1/+6 | |
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-10-29 | Add forward declaration header for build state types | Boris Kolpackov | 1 | -2/+1 | |
2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -1/+1 | |
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/+106 | |