build2 - build2 build system

Age	Commit message (Collapse)	Author	Files	Lines
2020-03-05	Use utf8_validator for buildfile and testscript lexers	Karen Arutyunov	1	-2/+5

2020-02-26	Adapt to adding validator to butl::char_scanner	Karen Arutyunov	1	-2/+2

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

2019-11-15	Generalize attributes to be comma-separated with arbitrary values	Boris Kolpackov	1	-4/+6
	Before: x = [string null] After: x = [string, null]
2019-11-14	Cleanup attribute parsing code	Boris Kolpackov	1	-2/+0

2019-11-14	Tighten up attribute recognition during parsing	Boris Kolpackov	1	-15/+31
	Now it should be possible to use `[]` for wildcard patterns, for example: foo = foo.[hit]xx Note that a leading bracket expression will still be recognized as attributes and escaping or quoting it will inhibit pattern matching. To resolve this case we need to specify an empty attribute list: foo = [] [abc]-foo.cxx
2019-11-11	Use path_name for `-` to stdin/stdout translation	Karen Arutyunov	1	-5/+5

2019-11-07	Initial work on path_name use for `-` to stdin/stdout translation	Boris Kolpackov	1	-7/+6

2019-11-04	Add support for configuration exporting and importing	Boris Kolpackov	1	-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-09-30	Reserve `:` in `case` pattern expression for future match extraction support	Boris Kolpackov	1	-1/+1

2019-09-30	Add support for custom match/extract functions in switch expression	Boris Kolpackov	1	-1/+5

2019-09-30	Add support for `case` pattern alternatives	Boris Kolpackov	1	-14/+18
	case <pattern>[ \| <pattern>...]
2019-09-30	Pattern matching support (switch): multiple values implementation	Boris Kolpackov	1	-10/+13

2019-07-01	Split build system into library and driver	Boris Kolpackov	1	-0/+207