commit | 4f969f8f198dc83ef9dc588084394cfa7efb9a49 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Sep 23 01:08:04 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Sep 23 01:08:04 2020 +0000 |
tree | 3607c76bf4ab6d75e2a598e120ad393f49df8568 | |
parent | 50094b1dd568650516d1527c49be2c013c3f76cc [diff] | |
parent | c14bf7ad42c9de1b5c45c9acd5d3cd263593c4c3 [diff] |
Merge remote-tracking branch 'aosp/upstream' am: f38eda59a8 am: e09f8a48e8 am: a5923ae3e1 am: c14bf7ad42 Original change: https://android-review.googlesource.com/c/platform/build/blueprint/+/1434328 Change-Id: Ib6cf2f1021c8ca8801d3364afe766a62f2f81f6f
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.