commit | ec5085e613aefc6f3e4037823bd67d9caed804f0 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Sun Apr 19 15:20:02 2020 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Sun Apr 19 15:20:02 2020 -0700 |
tree | 26c2232f8dbd11357a7167e5056f2b611d324a80 | |
parent | 5ef2a1eeaac689e76d4d6f7ec435065ed5c7f103 [diff] | |
parent | 2a062a2ef03631110e29b9c415aa30e81a4c5614 [diff] |
Merge remote-tracking branch 'aosp/upstream' * aosp/upstream: Actually write an empty ninja file with --empty-ninja-file Test: treehugger (build_test) Change-Id: Iff7851f2aa39eb14b7ae72ed6ce94fa0ce8d2621
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.