aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/module.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-09-08Get rid of warning in static buildBoris Kolpackov1-0/+2
2020-09-08Allow external modules that require bootstrapBoris Kolpackov1-13/+34
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-9/+9
2020-08-16Redo modules map as vectorBoris Kolpackov1-20/+38
2020-06-15Diagnose building of module or ad hoc C++ recipe using static build systemBoris Kolpackov1-13/+29
2020-06-10Fix bootstrap buildBoris Kolpackov1-0/+4
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-138/+180
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-9/+37
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-31Switch to project variable visibility by defaultBoris Kolpackov1-1/+1
2020-02-11Add match_only flag to contextBoris Kolpackov1-0/+1
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov1-3/+12
2020-01-28Use scope::var_pool()Boris Kolpackov1-2/+2
2020-01-27Improve module loading APIBoris Kolpackov1-2/+38
2019-11-07Use `lib` prefix on MinGW when forming build system module library nameBoris Kolpackov1-1/+3
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-1/+1
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-10-25Add --silent, remap verbosity 0 to 1 while building modules unless silentBoris Kolpackov1-0/+15
Failed that, we may have long periods of seemingly nothing happening (e.g., during implicit bdep sync) while we quietly update the module, which may look like things have hung up.
2019-10-23Un-tune scheduler when building build system modulesBoris Kolpackov1-1/+15
2019-10-22Handle invalid_argument when constructing build system module project nameBoris Kolpackov1-1/+9
2019-10-22Implement loaded_modules state lockingBoris Kolpackov1-0/+13
This would be necessary if someone runs two parallel top-level contexts.
2019-10-22Minor fixesBoris Kolpackov1-1/+1
2019-10-22Add load_builtin_module()Boris Kolpackov1-0/+7
2019-10-22Rename global_mutex_shards to global_mutexesBoris Kolpackov1-2/+2
2019-10-22Add tracing to find_module() and import_module()Boris Kolpackov1-1/+20
2019-10-22Move global mutex shards to contextBoris Kolpackov1-2/+3
2019-08-30Cutoff diagnostics stack when switching to nested contextBoris Kolpackov1-24/+36
2019-08-28Move cxx build system module to separate libraryKaren Arutyunov1-0/+1
2019-08-28Move c build system module to separate libraryKaren Arutyunov1-0/+1
2019-08-28Move cc build system module to separate libraryKaren Arutyunov1-0/+1
2019-08-28Move bin build system module to separate libraryKaren Arutyunov1-0/+1
2019-08-27Propagate global var overrides to module build contextBoris Kolpackov1-6/+6
2019-08-26Improve diagnostics in import_module()Boris Kolpackov1-20/+25
2019-08-26Implement updating build system modulesBoris Kolpackov1-23/+153
2019-08-23Introduce notion of build contextBoris Kolpackov1-2/+2
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-23Disable dynamic build system module loading in bootstrap buildBoris Kolpackov1-6/+17
We don't really need it so why jump through hoops like trying to portably link -ldl, etc.
2019-08-21Implement dynamic loading of build system modulesBoris Kolpackov1-38/+269
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+147
generated by cgit v1.1 at 2024-11-27 23:27:45 +0000