| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 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 | |
| 2019-08-26 | Factor target name processing code from parser to scope | Boris Kolpackov | 1 | -50/+4 | |
| 2019-08-26 | Make target types project-wide | Boris Kolpackov | 1 | -1/+1 | |
| 2019-08-25 | Split import into search and load steps | Boris Kolpackov | 1 | -4/+0 | |
| This allows us to load things in a separate context. | |||||
| 2019-08-23 | Introduce notion of build context | Boris Kolpackov | 1 | -35/+35 | |
| 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 | Cleanup context.hxx and its usage | Boris Kolpackov | 1 | -1/+0 | |
| 2019-08-16 | Minor cleanups | Boris Kolpackov | 1 | -3/+3 | |
| 2019-07-25 | Implement pre-parse mode for parse_names_trailer() | Karen Arutyunov | 1 | -2/+22 | |
| 2019-07-25 | Fix parse_names_trailer() for 'cross with empty LHS' case ({$empty}{x y}) | Karen Arutyunov | 1 | -0/+1 | |
| 2019-07-01 | Split build system into library and driver | Boris Kolpackov | 1 | -0/+5526 | |
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |