commit | 63085f9e7c138f15f3edec5e38d7c750a346cfe1 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Tue May 12 18:55:39 2020 -0700 |
committer | Colin Cross <ccross@android.com> | Tue May 12 19:20:26 2020 -0700 |
tree | c1e6e4eafbdd587ba267861d0898695798379e2d | |
parent | b0fe51a0c2724ab9b44e015c5fc7bf0f747847f6 [diff] |
Always emit rules for tests and add phony to run them Emit the rules to build blueprint tests even if runGoTests is not set, and add a phony rule "blueprint_tests" to run them. This will allow Soong to stop running the tests at the beginning of every build but still run them as part of checkbuild or with a manual `m blueprint_tests`. Bug: 156428456 Test: m Test: m blueprint_tests Change-Id: If293a0757766d3046e78bf230a1825f15adc68fd
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.