commit | 1cb6f844c553afebbc5fb71bb4a0ebff04278bdb | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Jan 11 07:34:02 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Jan 11 07:34:02 2020 +0000 |
tree | 0b66e95bcbd60b309d54a9f79be617326517f3f8 | |
parent | a02b6b638f981a7103d9a25105cfd54be968c496 [diff] | |
parent | ca01e7e98faa1830e20d7fb8641011bdabc98b17 [diff] |
Merge remote-tracking branch 'aosp/upstream' into master am: de71320aa6 am: 1b5f9af317 am: ca01e7e98f Change-Id: Idb952836d4e88257d1e09ea5f1cacfd6eae58bd4
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.