aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/dist/operation.cxx
AgeCommit message (Collapse)AuthorFilesLines
2022-11-08Make process exit diagnostics consistentBoris Kolpackov1-5/+13
In particular, we now always print error message on non-0 exit except in cases where such exit is ignored.
2022-11-08More work on child process diagnostics bufferingBoris Kolpackov1-15/+17
2022-10-19Add support for post hoc prerequisitesBoris Kolpackov1-14/+16
Unlike normal and ad hoc prerequisites, a post hoc prerequisite is built after the target, not before. It may also form a dependency cycle together with normal/ad hoc prerequisites. In other words, all this form of dependency guarantees is that a post hoc prerequisite will be built if its dependent target is built. See the NEWS file for details and an example.
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov1-1/+1
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-06Add ability to remap paths in distributionBoris Kolpackov1-28/+82
Specifically, the dist target-specific variable now can specify a path besides true or false. This path is the "imaginary" source location which is used to derive the corresponding distribution local. This location can be either a directory path (to remap with the same file name) or a file path (to remap with a different name). If the path is relative, then it's treated relative to the target directory. Note that to make things less error prone, simple paths without any directory separators are not allowed (use ./<name> instead). Note that if multiple targets end up with the same source location, the behavior is undefined and no diagnostics is issued. Note also that such remapping has no effect in the bootstrap distribution mode.
2022-07-21Don't issue conditional dependency declaration warning for imported projectsBoris Kolpackov1-2/+26
2022-05-27Don't pass --format to OpenBSD tar (ustar is default)Boris Kolpackov1-22/+25
2022-05-06Minor terminology fix in diagnostics and commentsBoris Kolpackov1-2/+2
2022-04-19Switch to using std::function for target::data_padBoris Kolpackov1-1/+1
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov1-1/+6
Note that the unmatch (match but do not update) and match (update during match) values are only supported by certain rules (and potentially only for certain prerequisite types). Additionally: - All operation-specific variables are now checked for false as an override for the prerequisite-specific include value. In particular, this can now be used to disable a prerequisite for update, for example: ./: exe{test}: update = false - The cc::link_rule now supports the update=match value for headers and ad hoc prerequisites. In particular, this can be used to make sure all the library headers are updated before matching any of its (or dependent's) object files.
2021-12-16Pass context to (meta-)operation hooksBoris Kolpackov1-9/+9
2021-11-16Ignore (with warning) directory symlink cycles in bootstrap distBoris Kolpackov1-3/+44
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov1-2/+2
2021-04-02Add support for propagating project environmentBoris Kolpackov1-0/+7
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-3/+5
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-1/+1
2021-01-30Rework include translation supportBoris Kolpackov1-2/+0
See the config.cxx.translate_include variable documentation in cxx/init.cxx for details.
2020-11-02Set executable bit for ad hoc buildscript rule executable target on POSIXKaren Arutyunov1-1/+1
2020-10-07Add ability to specify extra adhoc files for distributionBoris Kolpackov1-5/+39
2020-09-29Add bootstrap distribution mode (!config.dist.bootstrap=true)Boris Kolpackov1-195/+347
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-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-4/+4
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-1/+1
2020-02-12Add convenience run_start() overloadBoris Kolpackov1-1/+1
2020-02-11Add match_only flag to contextBoris Kolpackov1-41/+44
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-27Improve module loading APIBoris Kolpackov1-2/+2
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-1/+2
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-2/+1
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-2/+2
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-3/+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-10-01Adapt to moving path match to path-pattern.?xxKaren Arutyunov1-1/+1
2019-10-01Adapt to swapping of entry and pattern parameters in butl::path_match()Karen Arutyunov1-1/+1
2019-08-23Introduce notion of build contextBoris Kolpackov1-23/+29
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-05Move config, dist, test, and install modules into libraryKaren Arutyunov1-0/+868
generated by cgit v1.1 at 2024-11-01 16:22:53 +0000