| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2020-05-27 | Improve ternary diagnostics with info for wildcard pattern escape | Boris Kolpackov | 1 | -2/+13 | |
| 2020-05-01 | Fix outstanding issue with directive vs assignment differentiation | Boris Kolpackov | 1 | -6/+14 | |
| Specifically, now the following does the right thing: print +foo | |||||
| 2020-04-30 | Rename target::member to target::adhoc_member | Boris Kolpackov | 1 | -2/+2 | |
| 2020-04-27 | Rework tool importation along with cli module | Boris Kolpackov | 1 | -55/+107 | |
| 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-27 | Don't switch projects when switching scopes during bootstrap | Boris Kolpackov | 1 | -5/+13 | |
| 2020-04-27 | Fix assertion failure when name extension pattern is used | Karen Arutyunov | 1 | -0/+4 | |
| 2020-04-08 | Allow configuration variables in unnamed projects | Boris Kolpackov | 1 | -9/+27 | |
| 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-03-31 | Handle duplicate config directives for same variable | Boris Kolpackov | 1 | -1/+18 | |
| 2020-03-31 | Switch to project variable visibility by default | Boris Kolpackov | 1 | -2/+3 | |
| 2020-03-27 | Fix bug in previous commit | Boris Kolpackov | 1 | -2/+2 | |
| 2020-03-27 | Implement project configuration reporting, similar to build system modules | Boris Kolpackov | 1 | -85/+186 | |
| 2020-03-26 | Make buildfile parser reset'able | Boris Kolpackov | 1 | -12/+32 | |
| 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-25 | Enforce config directives only appearing in project's root.build | Boris Kolpackov | 1 | -6/+7 | |
| 2020-03-20 | Initial implementation of config directive for project-specific configuration | Boris Kolpackov | 1 | -1/+135 | |
| 2020-03-20 | Lexer support for default value assignment (?=) | Boris Kolpackov | 1 | -0/+10 | |
| Note: not yet supported in the parser. | |||||
| 2020-03-18 | Cleanup variable type/visibility/overridability logic | Boris Kolpackov | 1 | -40/+54 | |
| 2020-03-18 | Get rid of old and unused logic | Boris Kolpackov | 1 | -30/+5 | |
| 2020-03-17 | Rename all find*(variable) to lookup*(variable) | Boris Kolpackov | 1 | -2/+2 | |
| 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-02-07 | Drop copyright notice from source code | Karen Arutyunov | 1 | -1/+0 | |
| 2020-01-28 | Use scope::var_pool() | Boris Kolpackov | 1 | -3/+3 | |
| 2020-01-27 | Improve module loading API | Boris Kolpackov | 1 | -1/+1 | |
| 2020-01-27 | Improve process run_*() API | Boris Kolpackov | 1 | -9/+6 | |
| 2019-11-15 | Test and document wildcard character escaping | Boris Kolpackov | 1 | -1/+1 | |
| Also document the new bracket expression ([...]) wildcard support. | |||||
| 2019-11-15 | Generalize attributes to be comma-separated with arbitrary values | Boris Kolpackov | 1 | -45/+77 | |
| Before: x = [string null] After: x = [string, null] | |||||
| 2019-11-14 | Cleanup attribute parsing code | Boris Kolpackov | 1 | -48/+28 | |
| 2019-11-14 | Require attributes to be separated from words and similar on RHS | Boris Kolpackov | 1 | -2/+19 | |
| 2019-11-14 | Tighten up attribute recognition during parsing | Boris Kolpackov | 1 | -78/+111 | |
| 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-11 | Use path_name for `-` to stdin/stdout translation | Karen Arutyunov | 1 | -17/+18 | |
| 2019-11-07 | Initial work on path_name use for `-` to stdin/stdout translation | Boris Kolpackov | 1 | -2/+2 | |
| 2019-11-05 | Cosmetic change | Boris Kolpackov | 1 | -2/+2 | |
| 2019-11-05 | Fix function call diagnostics to use diag_frame | Boris Kolpackov | 1 | -15/+11 | |
| 2019-11-04 | Add support for configuration exporting and importing | Boris Kolpackov | 1 | -3/+8 | |
| 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-31 | Fix crashing on unhandled invalid_path thrown by parser::parse_include() | Karen Arutyunov | 1 | -17/+36 | |
| 2019-10-09 | Prepend pattern search paths to PATH when running binutils | Boris Kolpackov | 1 | -5/+6 | |
| This way any dependent tools (such as mt.exe that is invoked by link.exe) are first search for in there. | |||||
| 2019-10-01 | Adapt to moving path match to path-pattern.?xx | Karen Arutyunov | 1 | -1/+2 | |
| 2019-10-01 | Adapt to swapping of entry and pattern parameters in butl::path_match() | Karen Arutyunov | 1 | -3/+3 | |
| 2019-09-30 | Fix bug in for-loop body evaluation | Boris Kolpackov | 1 | -6/+10 | |
| 2019-09-30 | Allow attributes in if-else, assert directive's conditions | Boris Kolpackov | 1 | -17/+25 | |
| 2019-09-30 | Cleanup inappropriate use of parse_variable_value() | Boris Kolpackov | 1 | -40/+42 | |
| 2019-09-30 | Handle attributes in switch value and pattern expressions | Boris Kolpackov | 1 | -2/+28 | |
| 2019-09-30 | Diagnose `case` and `default` outside `switch` | Boris Kolpackov | 1 | -1/+2 | |
| 2019-09-30 | Reserve `:` in `case` pattern expression for future match extraction support | Boris Kolpackov | 1 | -1/+11 | |
| 2019-09-30 | Add support for custom match/extract functions in switch expression | Boris Kolpackov | 1 | -46/+82 | |
| 2019-09-30 | Add support for `case` pattern alternatives | Boris Kolpackov | 1 | -8/+38 | |
| case <pattern>[ | <pattern>...] | |||||
| 2019-09-30 | Allow multiple `case` for single line/block | Boris Kolpackov | 1 | -34/+82 | |
| 2019-09-30 | Pattern matching support (switch): multiple values implementation | Boris Kolpackov | 1 | -23/+52 | |
| 2019-09-30 | Pattern matching support (switch): single value implementation | Boris Kolpackov | 1 | -45/+220 | |
| 2019-09-27 | Adapt to bracket expressions in wildcard patterns | Karen Arutyunov | 1 | -34/+48 | |
| 2019-08-26 | Improve diagnostics | Boris Kolpackov | 1 | -1/+1 | |
| 2019-08-26 | Fix typo | Karen Arutyunov | 1 | -1/+2 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |