commit | 4d83bc154168c9bf379b149b97e30ee5c563a1b3 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Tue Aug 08 16:40:32 2017 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Tue Aug 08 16:40:53 2017 -0700 |
tree | 51777037069c8333c433f7142441b6192e2ce404 | |
parent | 292ad22f52c3cc92719941717093e65d01ba6e25 [diff] | |
parent | 18a0d2e9b5d0c3f753e527da95e10779ed0f20fe [diff] |
Merge remote-tracking branch 'aosp/upstream' into master * aosp/upstream: Support custom trace functions Implement microfactory Config, Build Allow microfactory to be used as a package Stop passing path to microfactory source Test: m -j blueprint_tools Change-Id: I857aeb6970d4d51489513f6ea789064d0f9f6556
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.