| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2015-12-02 | Add support for optional configuration for cli module | Boris Kolpackov | 2 | -47/+101 | |
| 2015-12-02 | Don't write config.{loaded,configured} special variables to config.build | Boris Kolpackov | 1 | -0/+6 | |
| 2015-12-02 | Implement optional module loading | Boris Kolpackov | 30 | -193/+327 | |
| The syntax is: using? cli Now each module use results in two bool variables: <module>.loaded and <module>.configured. Also implement variable visibility (the above two variables are limited to project). | |||||
| 2015-12-01 | Use 'extension' variable to resolve extension for file{} | Boris Kolpackov | 7 | -78/+127 | |
| We now also check target type/pattern-specific variables. So the new usage is: cli{*}: extension = cli | |||||
| 2015-12-01 | Reimplement define as dynamic derivation rather than alias | Boris Kolpackov | 12 | -149/+83 | |
| New syntax: define cli: file The rationale is we need to be able to assign the file extension (using type/pattern-specific variables). And if it is an alias, we will assign it to the original target type. Note that we could still support aliases if we need to. Will need to bring back the id member in target_type that would normally point to itself but for an alias would point to the origin. | |||||
| 2015-12-01 | Implement support for definition target type aliases | Boris Kolpackov | 15 | -86/+246 | |
| For example: define cli=file Currently, the semantics is that of a real alias with only name differences that are used for display. See tests/define/buildfile for more use cases. | |||||
| 2015-12-01 | Override outer configuration install paths that contain package name | Boris Kolpackov | 3 | -32/+55 | |
| 2015-11-30 | Don't try to install targets from other projects | Boris Kolpackov | 3 | -2/+28 | |
| 2015-11-30 | Add install support | Boris Kolpackov | 2 | -5/+5 | |
| 2015-11-30 | Tighten unresolved group logic | Boris Kolpackov | 4 | -17/+39 | |
| Now a wildcard/fallback rule should explicitly detect and handle unresolved situation. | |||||
| 2015-11-30 | Implement dist support for including/excluding targets | Boris Kolpackov | 3 | -5/+19 | |
| For example: cxx{*-options}: dist = true | |||||
| 2015-11-30 | Implement target type/pattern-specific variables | Boris Kolpackov | 3 | -28/+115 | |
| For example: cxx{*-options}: dist = true 1. Only single '*' wildcard is supported, matches 0 or more characters. 2. If target type is not specified, it defaults to any target. 3. Appending (+=) is not allowed. 4. The value is expanded immediately in the context of the scope. 5. The more specific pattern (i.e., with the shortest "stem") is preferred. If the stem has the same length, then the last defined (but not redefined) pattern is used. This will probably have to change to become an error. See tests/variable/type-pattern for more examples. | |||||
| 2015-11-30 | Add cli{} prerequisite if cli.cxx{} group doesn't have any | Boris Kolpackov | 1 | -4/+7 | |
| This happens when we use the group only for setting cli.options. Not very clean. | |||||
| 2015-11-30 | Cosmetic change | Boris Kolpackov | 1 | -52/+52 | |
| 2015-11-29 | Allow for target group members to remain unresolved | Boris Kolpackov | 5 | -17/+27 | |
| This, for example, can happen when we have a fallback rule for dist(update) or configure(update). | |||||
| 2015-11-28 | Add support for dist | Boris Kolpackov | 2 | -12/+58 | |
| 2015-11-28 | Add support for name crosses, for example {hxx ixx cxx}{foo bar} | Boris Kolpackov | 2 | -31/+123 | |
| See tests/names for more examples. | |||||
| 2015-11-28 | Include export.build from loaded, src-amalgamated subprojects | Boris Kolpackov | 1 | -3/+25 | |
| 2015-11-28 | Bump version to 0.1.0 | Boris Kolpackov | 1 | -1/+1 | |
| 2015-11-28 | Fix separated { handling in names parser | Boris Kolpackov | 1 | -2/+2 | |
| 'foo/ {a b}' should be equivalent to 'foo/ a b', not 'foo/a foo/b'. | |||||
| 2015-11-24 | Add missing #include | Boris Kolpackov | 1 | -0/+1 | |
| 2015-11-24 | Account for dangling/inaccessible links | Boris Kolpackov | 1 | -1/+12 | |
| 2015-09-25 | Quote arguments with spaces in print_process() | Boris Kolpackov | 1 | -4/+17 | |
| 2015-09-11 | Use install::alisa_rule to ignore non-installable prerequisites | Boris Kolpackov | 5 | -9/+66 | |
| 2015-09-11 | Check amalgamation itself when searching for imported project | Boris Kolpackov | 1 | -1/+10 | |
| 2015-09-11 | Handle file io failures in parser | Boris Kolpackov | 4 | -84/+99 | |
| 2015-09-11 | Add support for unnamed projects | Boris Kolpackov | 2 | -5/+19 | |
| Sometimes (e.g., in bpkg configuration) we don't have a project name. In fact, it is not really a project; it can never be referenced in an import directive. So we now have a notion of an unnamed project. Such a project should still have the 'project' variable set first thing in bootstrap.build but its value should be empty. Note that we can still amalgamate such projects just liked named ones. | |||||
| 2015-09-11 | Preserve pairs in expansion | Boris Kolpackov | 1 | -0/+6 | |
| 2015-09-10 | Reimplement buildspec parsing to deal with eval context | Boris Kolpackov | 1 | -71/+108 | |
| In short, in buildspec, parens are treated as operation application rather than eval context unless double-quoted. So in 'clean(foo)' we have the clean operation on target foo while in '"clean(foo)"' we have target cleanfoo. Also, as a bonus, we can now do {clean update}(/long/target/name/). | |||||
| 2015-09-10 | Fix bug in names() chunking mode | Boris Kolpackov | 1 | -4/+4 | |
| 2015-09-10 | Add support for token pre-processing in lexer | Boris Kolpackov | 2 | -2/+21 | |
| 2015-09-10 | Add support for chunking name parsing | Boris Kolpackov | 2 | -11/+30 | |
| 2015-09-09 | For newline escaping, ignore whole thing instead of making it newline | Boris Kolpackov | 1 | -5/+4 | |
| To capture literal newline, use quoting. | |||||
| 2015-09-09 | Add support for quoting directive names | Boris Kolpackov | 6 | -48/+45 | |
| Now only unquoted, literal names are recognized as directives, for example: 'print' = abc print $print | |||||
| 2015-09-09 | Add initial support for function calls: $func(a b c) | Boris Kolpackov | 1 | -27/+59 | |
| Now it is just a stub that prints the function name and its argument. Currently only single argument can be passed (no value pack support yet). | |||||
| 2015-09-09 | Add support for evaluation context | Boris Kolpackov | 4 | -130/+204 | |
| For now it acts as just the value mode that can be enabled anywhere variable expansion is supported, for example: (foo=bar): And the primary use currently is to enable/test quoted and indirect variable expansion: "foo bar" = FOO BAR print $"foo bar" # Invalid. print $("foo bar") # Yeah, baby. foo = FOO FOO = foo print $($foo) Not that you should do something like this... | |||||
| 2015-09-09 | Reimplement double quote lexing to avoid "implied quote" trick | Boris Kolpackov | 2 | -104/+96 | |
| 2015-09-08 | Initial take on double quote support | Boris Kolpackov | 2 | -19/+93 | |
| Currently, $(foo)-style variable expansion is not supported. | |||||
| 2015-09-08 | Use mode stack in lexer | Boris Kolpackov | 3 | -24/+44 | |
| 2015-09-08 | Implement single quote support | Boris Kolpackov | 4 | -5/+47 | |
| 2015-09-08 | Move context-dependent functions from diagnostics to context | Boris Kolpackov | 6 | -184/+183 | |
| 2015-09-08 | Clean up lexer mode logic | Boris Kolpackov | 3 | -3/+4 | |
| 2015-09-08 | Rework diagnostics verbosity, add quiet mode/option | Boris Kolpackov | 32 | -156/+234 | |
| 2015-09-04 | Fix clang warnings | Boris Kolpackov | 2 | -3/+4 | |
| 2015-09-04 | Fix static initialization order issue | Boris Kolpackov | 2 | -4/+14 | |
| 2015-09-02 | Override duplicate generated C++ dependency prefix | Boris Kolpackov | 1 | -3/+12 | |
| 2015-09-02 | Remove stray space | Boris Kolpackov | 1 | -1/+1 | |
| 2015-09-01 | Minor changes | Boris Kolpackov | 2 | -4/+1 | |
| 2015-08-31 | Clean parser implementation | Boris Kolpackov | 2 | -59/+13 | |
| 2015-08-31 | Rework scoping logic | Boris Kolpackov | 28 | -246/+475 | |
| Now the src directory is entered into the scope map and points to the same scope as out. This means that targets that are in src, not out (e.g., source files) will "see" rules, variables, etc. This becomes important when we try, for example, to install a source file (say, a header) from src: we need the rule as well as the install.* variables. | |||||
 |
index : build2 | |
| build2 build system |
| aboutsummaryrefslogtreecommitdiff |