aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/module.cxx
AgeCommit message (Collapse)AuthorFilesLines
2024-10-08Add context-wide pre/post operation callbacksBoris Kolpackov1-2/+12
2023-05-09Add --load-only option in addition to --match-onlyBoris Kolpackov1-1/+1
This option has the effect of loading all the subdirectory buildfiles that are not explicitly included.
2023-04-19Fix several issues in build system module importation logicmodule-importBoris Kolpackov1-70/+212
2023-04-13Move cli module to libbuild2-cli libraryBoris Kolpackov1-0/+1
This is a temporary measure (until we unboundle this module) needed for in-process configure support in bpkg.
2023-04-05Allow creating context with bare minimum of initializationsBoris Kolpackov1-6/+6
This is used by bpkg to detect forwarded configurations without incurring the full context creation overhead.
2023-03-01Add support for installation manifestBoris Kolpackov1-0/+3
2022-11-30Reserve targets, variables to avoid rehashingBoris Kolpackov1-0/+7
2022-10-28Add ability to disable diagnostics buffering (--no-diag-buffer)Boris Kolpackov1-0/+1
2022-10-13Optimize by going straight to public variable pool where applicableBoris Kolpackov1-2/+2
2022-02-17Add support for cheaply starting parallel scheduler pre-tuned to serialBoris Kolpackov1-4/+5
2021-12-16Pass context to (meta-)operation hooksBoris Kolpackov1-5/+5
2021-08-18Fix bug in external module skipping logicBoris Kolpackov1-7/+5
2021-05-13Don't both mark the scheduler queue and enter sub-phaseBoris Kolpackov1-10/+1
2021-05-12Deal with helper thread starvation during phase switchingBoris Kolpackov1-0/+4
The implemented solution entails shadowing old phase queues so that helpers don't pick up old phase tasks and boosting the max_threads count so that we can create more helpers if all the existing ones are stuck in the old phase.
2021-04-02Add support for propagating project environmentBoris Kolpackov1-1/+3
2021-03-16Define intermediate build results file cache interfaceBoris Kolpackov1-0/+1
2021-01-13Make sure we don't work any existing tasks when building in module contextBoris Kolpackov1-0/+6
2020-09-24Add post-boot module functionBoris Kolpackov1-3/+24
2020-09-22Add ability to skip external modules during bootstrap (--no-external-modules)Boris Kolpackov1-33/+61
2020-09-09Expand notes on issues with build system modules that require bootstrapBoris Kolpackov1-0/+6
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
generated by cgit v1.1 at 2024-11-27 08:28:00 +0000