commit | c528a0d9234d0e6c4ca6e3d66685fde01d42f296 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Feb 26 21:39:13 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Feb 26 21:39:13 2020 +0000 |
tree | 2c97f1e62fc91b30eabfc9b1ee2026d3b7028531 | |
parent | 99ea7872376e0865e82ee42e28256657afce0d45 [diff] | |
parent | 59a3a23e92cb5baa54dce5515f4f0ec43edd7ec9 [diff] |
In kzip files, compilation unit paths should be relative to top. am: 59a3a23e92 Change-Id: I672f992dacbcbf0f0e83d5f111996f6f5486181d
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.