commit | 4a0fe087b105d9974be92d976656e8ad935eae5a | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Thu Oct 19 15:30:06 2017 -0700 |
committer | Colin Cross <ccross@android.com> | Thu Oct 19 15:33:11 2017 -0700 |
tree | 371628d85554fa605c295d86a9ccaf5ed1ce011f | |
parent | 5029114553522a0e4612b7eb82996c02683b5508 [diff] |
Finish switching blueprint back to the original Blueprints format An ill-fated experiment with using a format that was closer to Bazel left Blueprint preferring the original style, but documenting and using the new style. Update the documentation and run bpfmt -w. Test: builds Change-Id: I3fb70c8fa50c332da01cf5912b179c60d1638814
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.