| commit | 41f781de9e907a22af17fcbd512b6cedf738c335 | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Wed Nov 07 07:40:31 2018 -0800 |
| committer | Mark Salyzyn <salyzyn@google.com> | Wed Nov 07 14:50:33 2018 -0800 |
| tree | a13495786da378a509efbd3b8f340d720e5b72bb | |
| parent | 68b081fd5a48f8026b7a3307c78e92c8d1bb692b [diff] |
build_image: right size image problems. Neglected to correct for filesystem size in estimate for verity. To keep build space optimized and make sure that the existing image does not confuse the tools, remove the out_file after the test build image phase. Test: build Bug: 111302946 Change-Id: I360775d862d02a721d061bbc43e8b4e2f03bd01e
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.