| commit | b247893deb8bd38dc8638f91797acea974a0142d | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Apr 14 16:10:21 2015 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Apr 14 16:21:53 2015 -0700 |
| tree | e3a5460033049ef6249537bc64ec22fecaf200e6 | |
| parent | 11bcca909896598024a68da33fc0fb8e419b2644 [diff] |
Fix misparsed $ after variable name
If a $ sign occurs after a variable name, the ninja string parser
fails to check if it is a $$ or a ${. Go to the
parseDollarStartState instead of the parseDollarState.
Since it is not yet known if the $ is the beginning of a new
variable (${ or $<alphanumeric>) or a string ($$), an empty string
separator cannot be added to the ninjaString strings list. Instead,
add functions to push strings or variables onto the ninjaString,
and automatically add the blank separator if two variables are
pushed in a row.
Change-Id: Ia1cae6259b1d7e4f633f61b9eadb2a2028bbd5f0
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja manifest describing the commands that need to be run and their dependencies. Where most build systems use built-in rules or a domain-specific language to describe the logic for converting module descriptions to build rules, Blueprint delegates this to per-project build logic written in Go. For large, heterogenous projects this allows the inherent complexity of the build logic to be maintained in a high-level language, while still allowing simple changes to individual modules by modifying easy to understand Blueprints files.