aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/file.cxx
AgeCommit message (Collapse)AuthorFilesLines
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=-
2019-10-22Minor fixesBoris Kolpackov1-1/+1
2019-10-22Move global mutex shards to contextBoris Kolpackov1-4/+4
2019-08-26Implement auto-import of development build2 buildBoris Kolpackov1-5/+28
2019-08-26Fix bug in import_search()Boris Kolpackov1-2/+2
2019-08-26Make target types project-wideBoris Kolpackov1-3/+4
2019-08-25Split import into search and load stepsBoris Kolpackov1-45/+78
This allows us to load things in a separate context.
2019-08-23Introduce notion of build contextBoris Kolpackov1-87/+106
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-21Implement dynamic loading of build system modulesBoris Kolpackov1-1/+1
2019-08-16Minor cleanupsBoris Kolpackov1-3/+1
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+1660