Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2020-03-25 | Enforce config directives only appearing in project's root.build | Boris Kolpackov | 1 | -28/+36 | |
2020-03-17 | Rename all find*(variable) to lookup*(variable) | Boris Kolpackov | 1 | -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-13 | Cleanup and make config/utility.?xx part of build system core | Boris Kolpackov | 1 | -5/+157 | |
2020-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
2020-01-28 | Use scope::var_pool() | Boris Kolpackov | 1 | -1/+1 | |
2020-01-27 | Improve module loading API | Boris Kolpackov | 1 | -2/+2 | |
2019-11-11 | Use path_name for `-` to stdin/stdout translation | Karen Arutyunov | 1 | -14/+17 | |
2019-11-07 | Initial work on path_name use for `-` to stdin/stdout translation | Boris Kolpackov | 1 | -2/+5 | |
2019-11-05 | Add support for automatic importing of libbuild2 of installed case | Boris Kolpackov | 1 | -0/+3 | |
2019-11-04 | Add support for configuration exporting and importing | Boris Kolpackov | 1 | -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-22 | Minor fixes | Boris Kolpackov | 1 | -1/+1 | |
2019-10-22 | Move global mutex shards to context | Boris Kolpackov | 1 | -4/+4 | |
2019-08-26 | Implement auto-import of development build2 build | Boris Kolpackov | 1 | -5/+28 | |
2019-08-26 | Fix bug in import_search() | Boris Kolpackov | 1 | -2/+2 | |
2019-08-26 | Make target types project-wide | Boris Kolpackov | 1 | -3/+4 | |
2019-08-25 | Split import into search and load steps | Boris Kolpackov | 1 | -45/+78 | |
This allows us to load things in a separate context. | |||||
2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -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-21 | Implement dynamic loading of build system modules | Boris Kolpackov | 1 | -1/+1 | |
2019-08-16 | Minor cleanups | Boris Kolpackov | 1 | -3/+1 | |
2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+1660 | |