commit | 9f179fcc6b0177773b584e6bd007625da2c48cfb | [log] [tgz] |
---|---|---|
author | Xin Li <delphij@google.com> | Wed Aug 14 13:43:04 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Aug 14 13:43:04 2019 -0700 |
tree | 95c4a9523457d2f0b437203e83e5646eac55f471 | |
parent | fc1915afaa00f9caf7442f672c6f2ca485f4caa6 [diff] | |
parent | 23721d6ca6f8a7d555692f208d29b3a546f36c26 [diff] |
[automerger skipped] DO NOT MERGE - Skip qt-dev-plus-aosp-without-vendor (5713463) in stage-aosp-master am: 8f656270df -s ours am: 23721d6ca6 Change-Id: Ib63f90d1c510be6d1f3bab8a9b0d3b5354749cb9
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.