aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/parser.hxx
AgeCommit message (Collapse)AuthorFilesLines
2020-05-27Add support for value subscript after expansionsBoris Kolpackov1-1/+8
Value subscript is only recognized in evaluation contexts (due to ambiguity with wildcard patterns; consider: $x[123].txt) and should be unseparated from the previous token. For example: x = ($y[1]) x = (($f ? $y : $z)[1]) x = ($identity($y)[$z])
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-7/+36
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-9/+17
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-04-27Don't switch projects when switching scopes during bootstrapBoris Kolpackov1-8/+2
2020-03-27Implement project configuration reporting, similar to build system modulesBoris Kolpackov1-13/+24
2020-03-26Make buildfile parser reset'ableBoris Kolpackov1-9/+23
Note that the testscript parser (which derives from the buildfile parser) is (still) not reset'able (this functionality is currently not needed so why complicate things).
2020-03-25Enforce config directives only appearing in project's root.buildBoris Kolpackov1-5/+11
2020-03-20Initial implementation of config directive for project-specific configurationBoris Kolpackov1-0/+3
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov1-3/+3
Before: x = [string null] After: x = [string, null]
2019-11-14Cleanup attribute parsing codeBoris Kolpackov1-0/+7
2019-11-14Tighten up attribute recognition during parsingBoris Kolpackov1-2/+9
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-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-10/+13
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-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-10-29Add forward declaration header for build state typesBoris Kolpackov1-5/+1
2019-09-30Allow attributes in if-else, assert directive's conditionsBoris Kolpackov1-1/+2
2019-09-30Handle attributes in switch value and pattern expressionsBoris Kolpackov1-0/+8
2019-09-30Add support for custom match/extract functions in switch expressionBoris Kolpackov1-6/+15
2019-09-30Allow multiple `case` for single line/blockBoris Kolpackov1-1/+7
2019-09-30Pattern matching support (switch): single value implementationBoris Kolpackov1-0/+9
2019-08-23Introduce notion of build contextBoris Kolpackov1-1/+5
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-25Implement pre-parse mode for parse_names_trailer()Karen Arutyunov1-0/+3
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+673