commit | 4334d39a227d263aa1892b2fea495195e8ca8997 | [log] [tgz] |
---|---|---|
author | Jeff Gaston <jeffrygaston@google.com> | Thu Nov 02 13:41:10 2017 -0700 |
committer | Jeff Gaston <jeffrygaston@google.com> | Thu Nov 02 13:56:32 2017 -0700 |
tree | ae32840d3b0cdae13164bcd11570a04586027c3b | |
parent | eb6192cf669ca2a0db71dcd41674fdfc6a6563c4 [diff] |
Update microfactory compile error message to show the command that failed Easier to debug than "Failed to compile: main: exit status 2" Bug: 68770962 Test: sed -i 's/build.FindSources/files := build.FindSources/' build/soong/cmd/soong_ui/main.go \ && m -j nothing Change-Id: If78a4fa1c3999e7c658dce072c05d7d3e23b8683
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.