| commit | cc57d31c91dcc67f8f5261c22ec5ca5c03572cfe | [log] [tgz] |
|---|---|---|
| author | xunchang <xunchang@google.com> | Fri Dec 07 12:12:17 2018 -0800 |
| committer | xunchang <xunchang@google.com> | Mon Dec 10 19:53:38 2018 -0800 |
| tree | e8b5cd022a1c891b5c5495bba954689c80226d84 | |
| parent | 19e65028847461c3ac922aaad68efc79c4bd41ea [diff] |
recovery text image: use zopflipng to compress the generated images Generate the images for recovery's wipe data menu. And use the lossless tool zopflipng to compress the generated image. This saves space in the boot image at the cost of the increase of build time. In practice, it adds about ~20 seconds to build the bootimage with 32 threads. zopflipng generally runs slower. Even with a predefined filters strategy, it runs about 3 times slower than pngcrush, e.g. ~40s vs 15s to compress a 1.8M png file. However, zopflipng also gives a better compression: ~1.4M vs 1.6M for the same image. So I guess the time consumption is a price worth paying. Bug: 74397117 Test: build the bootimage and check the resource images Change-Id: I3e71f8bedd3c183a3374b1a9464bf05500e1aa61
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.