| commit | 90339f95634f9d7f5c66b2736a51e8465350ba0f | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Tue Sep 08 15:49:42 2020 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Tue Sep 08 16:55:43 2020 +0800 |
| tree | 82c1d816182aaee2c504e14c83ddd46e15d3a7fc | |
| parent | 49fe034137e023dc9fe0bf4839f0c7ba9691dfe6 [diff] |
Disable sparse image for GSI products There are a couple of use cases where we don't want sparse image: 1. `DynamicSystemInstallationService` in Q framework doesn't support sparse images. 2. Super image manipulation tools (like `lpadd`) doesn't play nice with sparse images. Force non-sparse GSI so we don't break backwards compatibility (1) and we don't need to write `simg2img` everywhere (2). Bug: 167695592 Test: Prepare a device flashed with Q framework Test: Build system.img and create system.img.zip; the image is non-sparsed Test: m tradefed-all && \ tradefed.sh run commandAndExit template/atest_local_min \ --template:map preparers=template/preparers/dsu-preparer \ --extra-file system-img.zip=out/.../system.img.zip \ --dynamic-system-update:disable-tear-down Change-Id: Ib7667165ce53e87eb86bc7d3f56c80a418123a62
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.