commit | 47113641cd52e7af8e6f4fa7fc42f2f4eff5950a | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Tue Oct 17 13:49:28 2017 -0700 |
committer | Colin Cross <ccross@android.com> | Tue Oct 17 13:50:49 2017 -0700 |
tree | 61e5691e0d4be034652b714c3f9084495418fb4a | |
parent | afa12b47440ddfae6af9d258ec80f7f5f0c53cd3 [diff] |
Allow rules to specify order-only dependencies Commands that contain tools that don't affect the build results may want an order-only dependency on the tool. Allow rules to specify order-only dependencies the same way they specify implicit dependencies. Test: builds Change-Id: I3e0f886ae047b0fadf7a5c0dfeb9827d2c5c411d
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.