aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/version
AgeCommit message (Collapse)AuthorFilesLines
2022-02-09Adapt version module to package dependency new representation syntaxKaren Arutyunov2-44/+86
2022-02-07Use target::as instead of static_cast everywhereBoris Kolpackov1-1/+1
2021-11-03Add line processing customization hook to in::ruleBoris Kolpackov2-0/+5
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov3-4/+4
2021-08-13Cache git status results in version moduleBoris Kolpackov2-20/+30
2021-05-04Replace int_ with intf_ and imp_ with impl_ in namesBoris Kolpackov1-4/+4
2021-04-07Register environment variables for hermetic build configurationsBoris Kolpackov1-0/+6
2021-01-30Add std::{map, multimap} to types.hxxBoris Kolpackov1-3/+1
Seeing that std::map is becoming a common Buildfile variable type.
2020-11-06Fix snapshot extraction for subproject symlinked from git submoduleKaren Arutyunov1-3/+20
2020-11-02Set executable bit for ad hoc buildscript rule executable target on POSIXKaren Arutyunov1-1/+2
2020-10-15Add ability to specify fallback value for NULL substitutions with in.nullBoris Kolpackov2-3/+6
2020-09-29Add bootstrap distribution mode (!config.dist.bootstrap=true)Boris Kolpackov2-44/+41
In this mode the dist meta-operation does not load the project (but does bootstrap it) and adds all the source files into the distribution only ignoring files and directories that start with a dot. This mode is primarily meant for situation where the project cannot (yet) be loaded due to missing dependencies.
2020-08-26Fix bug in module initialization orderBoris Kolpackov1-2/+2
2020-08-17Add mvfile() filesystem utility functionBoris Kolpackov1-19/+7
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-2/+4
2020-07-02Cache project name in root_extraBoris Kolpackov1-8/+8
2020-06-12Make order of imports stable in saved host build configurationBoris Kolpackov1-0/+2
2020-04-27Require explicit variable type in scope::{assign,append}()Boris Kolpackov1-4/+5
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-8/+4
2020-03-25Diagnose unnamed project in version moduleBoris Kolpackov1-3/+6
2020-02-07Drop copyright notice from source codeKaren Arutyunov13-13/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov2-11/+11
2020-01-28Use scope::var_pool()Boris Kolpackov1-1/+1
2020-01-28Use scope::insert_rule()Boris Kolpackov1-11/+7
2020-01-27Improve module loading APIBoris Kolpackov2-7/+5
2020-01-27Improve process run_*() APIBoris Kolpackov1-1/+1
2019-11-29Fix bundled git running other git as a child on WindowsKaren Arutyunov1-9/+50
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov2-5/+5
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-0/+3
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-08-28Make lib{build2} "implied interface dependency" of modulesBoris Kolpackov1-5/+3
This makes our compilation and linking command lines a little bit saner.
2019-08-28Add/update some module descriptionsKaren Arutyunov1-1/+1
2019-08-28Move bin build system module to separate libraryKaren Arutyunov1-0/+4
2019-08-23Introduce notion of build contextBoris Kolpackov4-12/+25
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-21Cleanup context.hxx and its usageBoris Kolpackov2-1/+1
2019-08-20Add build.version.interfaceBoris Kolpackov1-2/+4
This build system interface version should be embedded into build system modules as load_suffix.
2019-08-15Embed build core version into build system modules as load pathBoris Kolpackov1-4/+9
2019-08-01Move version build system module to separate libraryKaren Arutyunov13-0/+1354
generated by cgit v1.1 at 2024-11-08 02:57:57 +0000