| commit | ba959a5ff1cc868512232a750e3e6cb6014a39e0 | [log] [tgz] |
|---|---|---|
| author | Yi-Yo Chiang <yochiang@google.com> | Thu Mar 18 18:50:03 2021 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Wed Mar 24 05:35:10 2021 +0000 |
| tree | 38efdafde89a3b879b9cb4e2a9493604208e56c0 | |
| parent | 26c77daaa458c7b4e5e3de9b69bd0d0c37577833 [diff] |
Add option to allow product makefiles to skip building super_empty.img This change doesn't change the condition for building super_empty.img, it just add a toggle PRODUCT_BUILD_SUPER_EMPTY_IMAGE that product makefiles can use to skip building super_empty.img. Products that don't use super_empty at all, for example GSI, can set this option to ensure the super_empty.img is not built. Bug: 183068624 Test: "m dist" on GSI and check the build artifacts under OUT and DIST directories, and check the contents of *-img-*.zip Change-Id: I54943952873d2d297fd9d18cbe14742bc12ae9c6
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.