path: root/libbuild2/file.cxx
AgeCommit message (Collapse)AuthorFilesLines
12 daysRegister environment variables for hermetic build configurationsBoris Kolpackov1-5/+25
2021-04-02Add support for propagating project environmentBoris Kolpackov1-5/+32
2021-03-19Redo entering of src directories into scope_mapBoris Kolpackov1-13/+13
2021-02-08Enter scope src directories into scope mapBoris Kolpackov1-16/+32
2021-01-12Diagnose typed and project-qualified empty namesBoris Kolpackov1-0/+5
2020-12-15Cache more results of executing programs (compilers, etc)Boris Kolpackov1-8/+23
2020-12-14Fix bug in create_new_target_locked()Karen Arutyunov1-1/+1
2020-11-13Minor tracing fix and additionBoris Kolpackov1-1/+1
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+1
2020-10-28Pad config report to maximum name lengthBoris Kolpackov1-10/+32
2020-09-24Give hints for common causes of "no rule to update ..." errorBoris Kolpackov1-1/+1
2020-09-24Add post-boot module functionBoris Kolpackov1-1/+10
2020-09-22Add ability to skip external modules during bootstrap (--no-external-modules)Boris Kolpackov1-1/+7
2020-09-15Handle infinite output when extracting metadata (GitHub issue #102)Boris Kolpackov1-2/+22
2020-08-26Fix bug in module initialization orderBoris Kolpackov1-21/+13
2020-08-24Only suggest ad hoc path import for path-based targetsBoris Kolpackov1-6/+10
2020-08-16Add ability to initialize bootstrapped modules after loading root.buildBoris Kolpackov1-5/+23
2020-08-16Redo modules map as vectorBoris Kolpackov1-8/+4
2020-07-12Cache subprojects variable value in scope::root_extraBoris Kolpackov1-35/+17
2020-07-10Add support for project-local importationBoris Kolpackov1-11/+19
An import without a project name or with the same name as the importing project's is now treated as importation from the same project. For example, given the libhello project that exports the lib{hello} target, a buildfile for an executable in the same project instead of doing something like this: include ../libhello/ exe{hello}: ../libhello/lib{hello} Can now do this: import lib = libhello%lib{hello} Or: import lib = lib{hello} And then: exe{hello}: $lib Note that a target in project-local importation must still be exported in the project's export stub. In other words, project-local importation goes through the same mechanisms as normal import.
2020-07-09Add support for ad hoc importationBoris Kolpackov1-68/+299
2020-07-08Fix bug in switch_scope()Boris Kolpackov1-1/+1
2020-07-03Cutoff amalgamation and subproject for simple projectsBoris Kolpackov1-40/+35
2020-07-02Optimize variable extraction in bootstrap_src()Boris Kolpackov1-64/+58
2020-07-02Cache project name in root_extraBoris Kolpackov1-8/+29
2020-06-09Make importation of unqualified targets illegalBoris Kolpackov1-6/+9
2020-06-09Move recipe build directory to build/build/recipes/Boris Kolpackov1-6/+9
Our new scheme is to have any "out" content in a subdirectory called build/ (build/build/ for the build system core, build/<module>/build/ for modules). This way we can ignore them in .gitignore with a generic entry.
2020-06-09Make metadata variable prefix mandatoryBoris Kolpackov1-28/+10
While we could automatically set it if the target is imported, there is nothing we can do if the target is used in the same project. So to avoid confusion we make it mandatory.
2020-06-03Add clarifying commentBoris Kolpackov1-0/+5
2020-06-01Extend target metadata to include variable prefix, stable nameBoris Kolpackov1-26/+76
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-18/+47
2020-05-27Amalgamation cutoff supportBoris Kolpackov1-44/+106
Now a project that disables amalgamation will not logically "see" an outer project even if it's physically inside its scope.
2020-04-30Verify path set by {src,out}-root.build files is absoluteBoris Kolpackov1-31/+50
2020-04-27Get rid of warningsBoris Kolpackov1-1/+1
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-136/+710
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-10/+12
2020-04-08Allow configuration variables in unnamed projectsBoris Kolpackov1-4/+13
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-04-08Document project-specific configuration supportBoris Kolpackov1-1/+2
2020-03-27Implement project configuration reporting, similar to build system modulesBoris Kolpackov1-0/+68
2020-03-27Share parser for loading root.build and pre/post hooksBoris Kolpackov1-25/+43
2020-03-25Enforce config directives only appearing in project's root.buildBoris Kolpackov1-28/+36
2020-03-17Rename all find*(variable) to lookup*(variable)Boris Kolpackov1-1/+1
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-03-13Cleanup and make config/utility.?xx part of build system coreBoris Kolpackov1-5/+157
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-28Use scope::var_pool()Boris Kolpackov1-1/+1
2020-01-27Improve module loading APIBoris Kolpackov1-2/+2
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-14/+17
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-2/+5
2019-11-05Add support for automatic importing of libbuild2 of installed caseBoris Kolpackov1-0/+3
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-24/+71
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=-