commit | 5f03f11c0a84f43ee680a5e68503d6dc280601ca | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Tue Nov 07 13:29:54 2017 -0800 |
committer | Colin Cross <ccross@android.com> | Tue Nov 07 13:31:33 2017 -0800 |
tree | 5cc9989ea43c6b873df4e7a02b5cf76e480d8860 | |
parent | e55004478ffbb70810386c8f8605b546eac39cd9 [diff] |
Add presingletons PreSingletons use the same interface as Singletons, but run after parsing all the blueprint files but before running any mutators or GenerateBuildActions. They can be used to perform global setup, including generating rules, that may be referenced by later mutator or generate passes. Test: m checkbuild Change-Id: I4b93425a724e739f5b8843262efb8804b3bf3531
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.