aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/dist
AgeCommit message (Collapse)AuthorFilesLines
2021-01-08Initial attempt (gzip -n and preserve post-processed manifest timestamp)reproducible-distBoris Kolpackov2-9/+16
Turns our this is not enough since tar saves timestamps (as well as owner information, file order, etc) including for directories and getting rid of that in a portable way is not going to be easy. Looks like the most plausible way would be to switch to embedded libarchive (provided it's possible to achieve everything we need).
2020-11-02Set executable bit for ad hoc buildscript rule executable target on POSIXKaren Arutyunov1-1/+1
2020-10-27Tweak dist rule to handle prerequisites outside projectBoris Kolpackov1-7/+21
2020-10-07Add ability to specify extra adhoc files for distributionBoris Kolpackov2-6/+58
2020-09-29Add bootstrap distribution mode (!config.dist.bootstrap=true)Boris Kolpackov4-233/+435
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-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-3/+1
2020-07-13Add ability to extend rule interface in source-compatible mannerBoris Kolpackov1-1/+1
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-03-31Switch to project variable visibility by defaultBoris Kolpackov1-9/+6
2020-03-17Rework config::{omitted,required,optional}() into unified config_lookup()Boris Kolpackov1-8/+11
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 Arutyunov8-8/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov3-19/+4
2020-01-28Use scope::var_pool()Boris Kolpackov1-1/+1
2020-01-28Use scope::insert_rule()Boris Kolpackov1-2/+2
2020-01-27See through lib{} group during distBoris Kolpackov1-2/+4
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 $config.export() functionBoris Kolpackov1-2/+1
This is similar to the config.export variable functionality except it can be called from within buildfiles. Note that this function can only be used during configure unless the config module creation was forced for other meta-operations with config.module=true in bootstrap.build.
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-28Add/update some module descriptionsKaren Arutyunov1-0/+5
2019-08-23Introduce notion of build contextBoris Kolpackov2-24/+30
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-24Move in build system module to separate libraryBoris Kolpackov2-3/+9
2019-07-05Move config, dist, test, and install modules into libraryKaren Arutyunov8-0/+1330
generated by cgit v1.1 at 2024-12-27 06:12:59 +0000