| commit | 90bfda1cc45643c302e80b99be3325d2e14b238c | [log] [tgz] |
|---|---|---|
| author | Isaac Chen <ycchen@google.com> | Fri Apr 12 13:16:34 2019 +0800 |
| committer | Isaac Chen <ycchen@google.com> | Fri Apr 12 13:16:34 2019 +0800 |
| tree | 4b108eb91fed6c81c867bef2ceb703c4e6093e6c | |
| parent | 289fa3cea303fa118365330e35b7758c4f4e72bd [diff] |
Change emulator system image to unsparse format
Currently, emulator system image is the non-legasy GSI, which is in sparse
format. Several internal clients don't support sparse format, and other
internal/external clients usually support both. The reason to choose sparse
format for GSI may not be valid any more. See bug for detail.
Bug: 130341962
Test: Checked the header of system.img to see if it's unsparse.
Boot emulator aosp_x86 successfully.
Boot mixed GSI and CF x86 successfully.
Change-Id: I839f49809429227607b2e876a4a3628df43a97b4
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.