aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/parser.hxx
AgeCommit message (Collapse)AuthorFilesLines
2024-01-09Allow imported buildfiles to using config.* variables from own projectBoris Kolpackov1-2/+7
2023-06-08Add support for buildfile importationBoris Kolpackov1-9/+9
2023-05-29Explicit group: syntax parsingBoris Kolpackov1-23/+14
2023-05-16Enter export stub targets with correct outBoris Kolpackov1-11/+9
2022-10-21Change attribute syntax in script to come after variable in set and for (set ↵Karen Arutyunov1-5/+15
x [...], for x [...])
2022-10-20Fix parser::mode() so for peeked token on replay it returns its lexing modeKaren Arutyunov1-2/+11
2022-10-14Fix 'for [<attrs>] x: ...' to treat <attrs> as value attributesKaren Arutyunov1-12/+0
2022-09-29Fix variable append logic in scriptBoris Kolpackov1-0/+12
2022-09-28Add support for 'for' loop first form (for x:...) in scriptKaren Arutyunov1-0/+10
2022-09-19Allow computed variables in depdb preamble similar to impure functionsBoris Kolpackov1-1/+1
2022-09-09Evaluate target specific variable assignment/block on ad hoc membersBoris Kolpackov1-2/+14
This is in preparation for (again) not treating primary member of an ad hoc group as a group for variable lookup.
2022-07-20Adjust conditional dependency declaration warning logicBoris Kolpackov1-8/+6
Now instead of ignoring imported stuff (which turned out to be racy), we only consider conditions up to the include boundary. The thinking here is that an included (but not sourced) buildfile is a standalone entity (e.g., imported project but also could be just a side-included buildfile). Note that unfortunately we will still be issuing warnings in imported projects since there is no straightforward way to know what is being distributed and what is not while parsing.
2022-07-19Warn about conditional dependency declarations during distributionBoris Kolpackov1-0/+9
2022-06-28Add support for querying out-qualified target-specific variablesBoris Kolpackov1-3/+7
2022-06-21Add --trace-{match,execute} optionsBoris Kolpackov1-5/+21
These options can be used to understand which dependency chain causes matching or execution of a particular target.
2022-06-14Add note to parser::lookup_variable() descriptionBoris Kolpackov1-0/+4
2022-06-03Expose type name to value_type mapping function in parserBoris Kolpackov1-0/+9
2022-05-02Don't verify parser replay integrity if exception is being thrownBoris Kolpackov1-3/+21
2022-04-06Add support for rule hintsBoris Kolpackov1-4/+11
A rule hint is a target attribute, for example: [rule_hint=cxx] exe{hello}: c{hello} Rule hints can be used to resolve ambiguity when multiple rules match the same target as well as to override an unambiguous match.
2022-02-14Add parser::parse_eval() public API functionBoris Kolpackov1-12/+18
2021-10-14Add ability to detect sole expansion in parser::parse_names()Boris Kolpackov1-2/+3
2021-09-20Assign pre-defined semantics to config.<project>.develop variablesBoris Kolpackov1-1/+5
This variable allows a project to distinguish between development and consumption builds. While normally there is no distinction between these two modes, sometimes a project may need to provide additional functionality during development. For example, a source code generator which uses its own generated code in its implementation may need to provide a bootstrap step from the pre-generated code. Normally, such a step is only needed during development. See "Project Configuration" in the manual for details.
2021-08-09Use parse_variable_name() in parse_import(), parse_config()Boris Kolpackov1-0/+3
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov1-0/+1
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov1-1/+2
An ad hoc pattern rule consists of a pattern that mimics a dependency declaration followed by one or more recipes. For example: exe{~'/(.*)/'}: cxx{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} If a pattern matches a dependency declaration of a target, then the recipe is used to perform the corresponding operation on this target. For example, the following dependency declaration matches the above pattern which means the rule's recipe will be used to update this target: exe{hello}: cxx{hello} While the following declarations do not match the above pattern: exe{hello}: c{hello} # Type mismatch. exe{hello}: cxx{howdy} # Name mismatch. On the left hand side of `:` in the pattern we can have a single target or an ad hoc target group. The single target or the first (primary) ad hoc group member must be a regex pattern (~). The rest of the ad hoc group members can be patterns or substitutions (^). For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} On the left hand side of `:` in the pattern we have prerequisites which can be patterns, substitutions, or non-patterns. For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} hxx{^'/\1/'} hxx{common} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} Substitutions on the left hand side of `:` and substitutions and non-patterns on the right hand side are added to the dependency declaration. For example, given the above rule and dependency declaration, the effective dependency is going to be: <exe{hello} file{hello.map>: cxx{hello} hxx{hello} hxx{common}
2021-05-28Add support for regex-based target type/pattern specific variablesBoris Kolpackov1-5/+9
This is in addition to the already supported path-based target type/pattern specific variables. For example: hxx{*}: x = y # path-based hxx{~/.*/}: x = y # regex-based
2021-05-28Add pattern_mode::ignore and use in appropriate placesBoris Kolpackov1-0/+1
2021-05-28Make notion of name pattern explicit, fix various related loose endsBoris Kolpackov1-5/+5
2021-04-07Register environment variables for hermetic build configurationsBoris Kolpackov1-0/+3
2021-04-02Add support for propagating project environmentBoris Kolpackov1-2/+3
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-1/+1
2020-12-08In update ad hoc recipe buildscripts allow non-pure function calls only in ↵Karen Arutyunov1-0/+7
depdeb preamble
2020-07-06Adjust variable block applicability in dependency chainsBoris Kolpackov1-3/+2
Before the block used to apply to the set of prerequisites before the last `:`. This turned out to be counterintuitive and not very useful since prerequisite-specific variables are a lot less common than target specific. And it doesn't fit with ad hoc recipes. The new rule is if the chain ends with `:`, then the block applies to the last set of prerequisites. Otherwise, it applies to the last set of targets. For example: ./: exe{test}: cxx{main} { test = true # Applies to the exe{test} target. } ./: exe{test}: libue{test}: { bin.whole = false # Applies to the libue{test} prerequisite. } This is actually consistent with both non-chain and non-block cases. Consider: exe{test}: cxx{main} { test = true } exe{test}: libue{test}: { bin.whole = false } exe{test}: libue{test}: bin.whole = false The only exception we now have in this overall approach of "if the dependency declaration ends with a colon, then what follows is for a prerequisite" is for the first semicolon: exe{test}: { test = true } exe{test}: test = true But that's probably intuitive enough since there cannot be a prerequisite without a target.
2020-06-10Handle special variable names when spelled as $(<char>) rather than $<char>Boris Kolpackov1-4/+21
2020-06-05Add ability to specify ad hoc recipe actionsBoris Kolpackov1-2/+2
We are reusing the buildspec syntax for that.
2020-06-03Factor implementation-specific ad hoc recipe parsing to adhoc_*_ruleBoris Kolpackov1-17/+17
2020-05-29Add support for is-else, switch in ad hoc recipesBoris Kolpackov1-1/+16
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