aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/parser.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-04-27Fix assertion failure when name extension pattern is usedKaren Arutyunov1-0/+4
2020-04-08Allow configuration variables in unnamed projectsBoris Kolpackov1-9/+27
While generally a bad idea, there are valid situations where this may happen, such as a standalone build of the tests subproject in test-installed.
2020-03-31Handle duplicate config directives for same variableBoris Kolpackov1-1/+18
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-2/+3
2020-03-27Fix bug in previous commitBoris Kolpackov1-2/+2
2020-03-27Implement project configuration reporting, similar to build system modulesBoris Kolpackov1-85/+186
2020-03-26Make buildfile parser reset'ableBoris Kolpackov1-12/+32
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-6/+7
2020-03-20Initial implementation of config directive for project-specific configurationBoris Kolpackov1-1/+135
2020-03-20Lexer support for default value assignment (?=)Boris Kolpackov1-0/+10
Note: not yet supported in the parser.
2020-03-18Cleanup variable type/visibility/overridability logicBoris Kolpackov1-40/+54
2020-03-18Get rid of old and unused logicBoris Kolpackov1-30/+5
2020-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov1-2/+2
Now we consistently use term "lookup" for variable value lookup. At some point we should also rename type lookup to binding and get rid of all the lookup_type aliases.
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-28Use scope::var_pool()Boris Kolpackov1-3/+3
2020-01-27Improve module loading APIBoris Kolpackov1-1/+1
2020-01-27Improve process run_*() APIBoris Kolpackov1-9/+6
2019-11-15Test and document wildcard character escapingBoris Kolpackov1-1/+1
Also document the new bracket expression ([...]) wildcard support.
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov1-45/+77
Before: x = [string null] After: x = [string, null]
2019-11-14Cleanup attribute parsing codeBoris Kolpackov1-48/+28
2019-11-14Require attributes to be separated from words and similar on RHSBoris Kolpackov1-2/+19
2019-11-14Tighten up attribute recognition during parsingBoris Kolpackov1-78/+111
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-17/+18
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-2/+2
2019-11-05Cosmetic changeBoris Kolpackov1-2/+2
2019-11-05Fix function call diagnostics to use diag_frameBoris Kolpackov1-15/+11
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-3/+8
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-31Fix crashing on unhandled invalid_path thrown by parser::parse_include()Karen Arutyunov1-17/+36
2019-10-09Prepend pattern search paths to PATH when running binutilsBoris Kolpackov1-5/+6
This way any dependent tools (such as mt.exe that is invoked by link.exe) are first search for in there.
2019-10-01Adapt to moving path match to path-pattern.?xxKaren Arutyunov1-1/+2
2019-10-01Adapt to swapping of entry and pattern parameters in butl::path_match()Karen Arutyunov1-3/+3
2019-09-30Fix bug in for-loop body evaluationBoris Kolpackov1-6/+10
2019-09-30Allow attributes in if-else, assert directive's conditionsBoris Kolpackov1-17/+25
2019-09-30Cleanup inappropriate use of parse_variable_value()Boris Kolpackov1-40/+42
2019-09-30Handle attributes in switch value and pattern expressionsBoris Kolpackov1-2/+28
2019-09-30Diagnose `case` and `default` outside `switch`Boris Kolpackov1-1/+2
2019-09-30Reserve `:` in `case` pattern expression for future match extraction supportBoris Kolpackov1-1/+11
2019-09-30Add support for custom match/extract functions in switch expressionBoris Kolpackov1-46/+82
2019-09-30Add support for `case` pattern alternativesBoris Kolpackov1-8/+38
case <pattern>[ | <pattern>...]
2019-09-30Allow multiple `case` for single line/blockBoris Kolpackov1-34/+82
2019-09-30Pattern matching support (switch): multiple values implementationBoris Kolpackov1-23/+52
2019-09-30Pattern matching support (switch): single value implementationBoris Kolpackov1-45/+220
2019-09-27Adapt to bracket expressions in wildcard patternsKaren Arutyunov1-34/+48
2019-08-26Improve diagnosticsBoris Kolpackov1-1/+1
2019-08-26Fix typoKaren Arutyunov1-1/+2
2019-08-26Factor target name processing code from parser to scopeBoris Kolpackov1-50/+4
2019-08-26Make target types project-wideBoris Kolpackov1-1/+1
2019-08-25Split import into search and load stepsBoris Kolpackov1-4/+0
This allows us to load things in a separate context.
2019-08-23Introduce notion of build contextBoris Kolpackov1-35/+35
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-21Cleanup context.hxx and its usageBoris Kolpackov1-1/+0
generated by cgit v1.1 at 2024-12-22 09:14:50 +0000