commit | 73ff57f48a7ac18f52980b0c6bf0f2bbd19423f1 | [log] [tgz] |
---|---|---|
author | Elliott Hughes <enh@google.com> | Wed Dec 06 12:16:39 2017 -0800 |
committer | Elliott Hughes <enh@google.com> | Wed Dec 06 12:16:39 2017 -0800 |
tree | c7a608d29ac38fa5a270eba3b551fe885e1965a1 | |
parent | 44e363f1e330e5a2f2f760897f2f57c0b975fc30 [diff] |
Explain why BuildImage failed. BuildImage can return false for lots of reasons. Log two of the more plausible ones. You'll still need to edit this file and pass True to RunCommand to work out *what* went wrong, but at least this logging will tell you *where* things went wrong. Bug: http://b/63142920 Test: debugged my actual problem Change-Id: If84427058108dcac0a1b5e2216b8bb11eef522ca
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.