commit | 24843621ce0afba05d8522d0604a62bb163cdcdb | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Thu Sep 24 02:11:25 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Sep 24 02:11:25 2020 +0000 |
tree | cef4043d9661ebb911504b5317d9dd19587f63a2 | |
parent | 4f969f8f198dc83ef9dc588084394cfa7efb9a49 [diff] | |
parent | 1cb0da07846a2e6517fd2e2f5211b634cef202b1 [diff] |
Merge remote-tracking branch 'aosp/upstream' am: f94644fe3d am: ac49845522 am: a92993f52c am: 1cb0da0784 Original change: https://android-review.googlesource.com/c/platform/build/blueprint/+/1435711 Change-Id: I739961edf2b851ee40944478cb778e14f85133d9
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.