build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2020-07-02	Cache project name in root_extra	Boris Kolpackov	1	-8/+8

2020-06-12	Make order of imports stable in saved host build configuration	Boris Kolpackov	1	-0/+2

2020-04-27	Require explicit variable type in scope::{assign,append}()	Boris Kolpackov	1	-4/+5

2020-03-31	Switch to project variable visibility by default	Boris Kolpackov	1	-8/+4

2020-03-25	Diagnose unnamed project in version module	Boris Kolpackov	1	-3/+6

2020-02-07	Drop copyright notice from source code	Karen Arutyunov	13	-13/+0

2020-01-29	Rename module_base to module, redo module boot/init argument passing	Boris Kolpackov	2	-11/+11

2020-01-28	Use scope::var_pool()	Boris Kolpackov	1	-1/+1

2020-01-28	Use scope::insert_rule()	Boris Kolpackov	1	-11/+7

2020-01-27	Improve module loading API	Boris Kolpackov	2	-7/+5

2020-01-27	Improve process run_*() API	Boris Kolpackov	1	-1/+1

2019-11-29	Fix bundled git running other git as a child on Windows	Karen Arutyunov	1	-9/+50

2019-11-15	Use path_name_view in location and path_name_value in location_value	Karen Arutyunov	2	-5/+5

2019-11-04	Add support for configuration exporting and importing	Boris Kolpackov	1	-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-28	Make lib{build2} "implied interface dependency" of modules	Boris Kolpackov	1	-5/+3
	This makes our compilation and linking command lines a little bit saner.
2019-08-28	Add/update some module descriptions	Karen Arutyunov	1	-1/+1

2019-08-28	Move bin build system module to separate library	Karen Arutyunov	1	-0/+4

2019-08-23	Introduce notion of build context	Boris Kolpackov	4	-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-21	Cleanup context.hxx and its usage	Boris Kolpackov	2	-1/+1

2019-08-20	Add build.version.interface	Boris Kolpackov	1	-2/+4
	This build system interface version should be embedded into build system modules as load_suffix.
2019-08-15	Embed build core version into build system modules as load path	Boris Kolpackov	1	-4/+9

2019-08-01	Move version build system module to separate library	Karen Arutyunov	13	-0/+1354