aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/build/script
AgeCommit message (Collapse)AuthorFilesLines
2023-05-29Explicit group: pattern membersBoris Kolpackov1-1/+1
2023-05-29Explicit group: dynamic membersBoris Kolpackov2-23/+82
2023-05-29Explicit group: static membersBoris Kolpackov4-24/+65
2023-05-21Add support for dynamic target extraction in addition to prerequisitesBoris Kolpackov7-96/+539
This functionality is enabled with the depdb-dyndep --dyn-target option. Only the make format is supported, where the listed targets are added as ad hoc group members (unless already specified as static members). This functionality is not available in the --byproduct mode.
2023-03-20Regenerate options parsing filesKaren Arutyunov1-0/+50
2022-11-25Use operation name as a buildscript name if unable to deduceKaren Arutyunov3-13/+22
2022-11-18Complete low verbosity diagnostics reworkBoris Kolpackov3-11/+12
2022-11-09Use diag_buffer in scriptKaren Arutyunov3-9/+13
2022-10-21Change attribute syntax in script to come after variable in set and for (set ↵Karen Arutyunov2-33/+49
x [...], for x [...])
2022-10-20Add support for for-loop element typeKaren Arutyunov1-1/+1
2022-10-18Fix unexpected 'unterminated double-quoted sequence' script errorKaren Arutyunov4-21/+23
2022-10-18Add unexpected 'unterminated double-quoted sequence' error testscript ↵Karen Arutyunov2-0/+26
reproducers
2022-10-18Invent diag preamble for buildscriptKaren Arutyunov5-108/+293
2022-10-14Fix 'for [<attrs>] x: ...' to treat <attrs> as value attributesKaren Arutyunov2-15/+15
2022-10-13Add support for 'for' loop second (... | for x) and third (for x <...) forms ↵Karen Arutyunov11-69/+868
in script
2022-10-10Preparatory work for public/private variable distinctionBoris Kolpackov4-11/+16
We still always use the public var_pool from context but where required, all access now goes through scope::var_pool().
2022-09-29Tighten low-verbosity diagnostics name deduction logicBoris Kolpackov1-3/+41
Specifically, don't try to derive low-verbosity name from what looks like an eval context of a function call.
2022-09-29Fix variable append logic in scriptBoris Kolpackov2-12/+29
2022-09-28Add support for 'for' loop first form (for x:...) in scriptKaren Arutyunov3-34/+271
2022-09-28Add support for 'while' loop in scriptKaren Arutyunov8-72/+324
2022-09-19Allow computed variables in depdb preamble similar to impure functionsBoris Kolpackov3-9/+49
2022-07-26Re-enable temporarily disable tests (part of cmdline work)Boris Kolpackov2-10/+2
2022-07-07Use new cmdline type for canned command lines in {Build,Test}scriptBoris Kolpackov2-45/+68
2022-07-01Regenerate options parsing filesKaren Arutyunov1-6/+35
2022-06-28Add support for querying out-qualified target-specific variablesBoris Kolpackov2-2/+2
2022-06-24Allow ad hoc rules not to list targets that are updated during matchBoris Kolpackov1-1/+8
For example, this allows a Qt moc rule not to list generated headers from libQtCore since they are pre-generated by the library.
2022-06-21Add --trace-{match,execute} optionsBoris Kolpackov1-3/+3
These options can be used to understand which dependency chain causes matching or execution of a particular target.
2022-05-23Cache build.host value in contextBoris Kolpackov1-1/+1
2022-03-11Add JSON format support for --structured-result option and info meta operationKaren Arutyunov2-4/+0
2022-03-07Add support for update=unmatch|match to ad hoc recipesBoris Kolpackov1-0/+13
2022-03-02Add update operation-specific variable with unmatch|match additional valuesBoris Kolpackov2-7/+7
Note that the unmatch (match but do not update) and match (update during match) values are only supported by certain rules (and potentially only for certain prerequisite types). Additionally: - All operation-specific variables are now checked for false as an override for the prerequisite-specific include value. In particular, this can now be used to disable a prerequisite for update, for example: ./: exe{test}: update = false - The cc::link_rule now supports the update=match value for headers and ad hoc prerequisites. In particular, this can be used to make sure all the library headers are updated before matching any of its (or dependent's) object files.
2022-02-21Factor process-wide initialization to init_process() functionBoris Kolpackov1-1/+1
2022-02-18Factor out common CLI types (scanners, etc)Karen Arutyunov6-919/+175
2022-02-16Invent quoting modes for to_stream(name)Karen Arutyunov1-1/+1
2022-02-10Make few global types separately constructible/initializableBoris Kolpackov1-1/+1
2022-01-18Add dynamic prerequisites to $< unless --adhoc is specifiedBoris Kolpackov7-30/+101
Also add a few tests for depdb-dyndep.
2022-01-06Add depdb-dyndep --update-{include,exclude} optionsBoris Kolpackov3-36/+327
These options specify prerequisite targets/patterns to include/exclude (from the static prerequisite set) for update during match as part of dynamic dependency extraction (those excluded will be updated during execute). For example: depdb dyndep ... --update-exclude libue{hello-meta} ... depdb dyndep ... --update-exclude libue{*} ... depdb dyndep ... --update-include $moc --update-include hxx{*} ... The order in which these options are specified is significant with the first target/pattern that matches determining the result. If only the --update-include options are specified, then only the explicitly included prerequisites will be updated. Otherwise, all prerequisites that are not explicitly excluded will be updated. If none of these options is specified, then all the static prerequisites are updated during match. Note also that these options do not apply to ad hoc prerequisites which are always updated during match.
2021-12-06Recognize absolute Windows paths in make parserBoris Kolpackov1-1/+1
2021-12-06Redo make_parser interface to return path, handle invalid_path exceptionBoris Kolpackov1-4/+2
2021-12-03Add depdb-dyndep --drop-cycles optionBoris Kolpackov6-27/+84
2021-11-30Add support for dynamic dependencies as byproduct of script bodyBoris Kolpackov7-159/+368
Specifically, the `depdb dyndep` builtin now has the --byproduct option (which must come first). In this mode only the --file input is supported. For example: obje{hello.o}: cxx{hello} {{ o = $path($>) t = $(o).t depdb dyndep --byproduct --what=header --default-type=h --file $t diag c++ ($<[0]) $cxx.path $cxx.poptions $cc.poptions $cc.coptions $cxx.coptions $cxx.mode -o $o -MD -MF $t -c $path($<[0]) }} Naturally, this mode does not support dynamic auto-generated prerequisites. If present, such prerequisites must be specified statically in the buildfile. Note also that the --default-prereq-type option has been rename to --default-type.
2021-11-23Add support for dynamic dependencies in ad hoc Buildscript recipesBoris Kolpackov10-94/+2501
Specifically, add the new `depdb dyndep` builtin that can be used to extract dynamic dependencies from a program run or a file. For example: obje{hello.o}: cxx{hello} {{ s = $path($<[0]) depdb dyndep $cxx.poptions $cc.poptions --what=header --default-prereq-type=h -- $cxx.path $cxx.poptions $cc.poptions $cxx.mode -M -MG $s diag c++ ($<[0]) o = $path($>) $cxx.path $cxx.poptions $cc.poptions $cc.coptions $cxx.coptions $cxx.mode -o $o -c $s }} Currently only the `make` dependency format is supported.
2021-10-14Disable re-parse of sole expansions in BuildscriptBoris Kolpackov3-3/+36
2021-10-14Pass along parse_names_result during script command parsingBoris Kolpackov2-12/+11
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov3-3/+3
2021-09-24Fortify tests against NDEBUGKaren Arutyunov2-2/+6
2021-08-04Take into account file-base'ness in ad hoc buildscript recipesBoris Kolpackov3-7/+17
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov3-22/+26
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov3-4/+6
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-06-08Only pass target to recipe_text() if recipe is not sharedBoris Kolpackov3-12/+19