| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2020-07-01 | Add *.export.imp_libs to get rid of dual *.export.libs semantics | Boris Kolpackov | 1 | -0/+1 | |
| 2020-06-09 | Move C++ modules sidebuild to build/cc/build/modules/ subdirectory | Boris Kolpackov | 1 | -8/+18 | |
| 2020-05-27 | Initial support for ad hoc recipes (still work in progress) | Boris Kolpackov | 1 | -3/+3 | |
| 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-03-31 | Switch to project variable visibility by default | Boris Kolpackov | 1 | -12/+12 | |
| 2020-03-17 | Rework config::{omitted,required,optional}() into unified config_lookup() | Boris Kolpackov | 1 | -7/+8 | |
| 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 | -16/+12 | |
| 2020-01-28 | Use scope::var_pool() | Boris Kolpackov | 1 | -27/+27 | |
| 2020-01-27 | Improve module loading API | Boris Kolpackov | 1 | -35/+16 | |
| 2019-10-21 | Add more information on C and C++ compiler mode options to manual | Boris Kolpackov | 1 | -0/+2 | |
| 2019-10-18 | Add ability to specify "compiler mode" options as part of config.{c,cxx} | Boris Kolpackov | 1 | -0/+10 | |
| Such options are (normally) not overridden by buildfiles and are passed last (after cc.coptions and {c,cxx}.coptions) in the resulting command lines. They are also cross-hinted between config.c and config.cxx. For example: $ b config.cxx="g++ -m64" | |||||
| 2019-08-28 | Move cc build system module to separate library | Karen Arutyunov | 1 | -0/+493 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |