commit | e5a91f55e4bc6d0a95c501bf398becfb116cec26 | [log] [tgz] |
---|---|---|
author | Yo Chiang <yochiang@google.com> | Thu Mar 05 11:12:42 2020 +0800 |
committer | Yo Chiang <yochiang@google.com> | Thu Mar 05 11:24:01 2020 +0800 |
tree | d7571a882a3174663b277d74418359a01ace4374 | |
parent | 03d3ee51f62c8453ed5d034579fc10a9ec4bd896 [diff] |
bpmodify: respect exitCode main() method calls os.Exit(exitCode) upon return, respecting any exitCode set by the report() method. Test: bpmodify -w; echo "$?" Test: bpmodify Android.bp; echo "$?" Test: # echo command should output "2" Change-Id: Iaf056301eaba3f249b256ecf0f0d87f8a4df1c58
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.