| commit | cb7b9ad6ca7dfa4affc0dda877a6a33dbc3baeb9 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Mon Mar 02 15:32:36 2015 -0800 |
| committer | Colin Cross <ccross@android.com> | Wed Mar 04 14:00:06 2015 -0800 |
| tree | 3266153ac876840335158726b5afeede867bede1 | |
| parent | d9d92cb75d40524df388d6e94497ebcf1c15d107 [diff] |
Go back to the old Blueprints file format
Switch back to:
moduleType {
name: value,
arch: {
x86: {
name: value,
},
},
}
This provides better consistency between properties defined at the
top level of a module and properties defined inside a map.
The parser will continue to support the other format for now, but the
printer will only produce the original format.
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja (http://martine.github.io/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 langauge 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.