| commit | f0cef8d8bfacd6776e3fa894f21a0876e414370d | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Mon Oct 29 10:55:06 2018 -0700 |
| committer | Mark Salyzyn <salyzyn@google.com> | Mon Oct 29 13:37:10 2018 -0700 |
| tree | 9974520ecdfcaac017bee2f157515ace47aa68ad | |
| parent | c3d408e3c180327bfbc88e9147e25bb793071bf6 [diff] |
build_image setup ext4 dedupe on more images. Add ext4 dedupe to system_other, product, product_services, odm and oem images. Experimental savings without any other configuration changes was 0%, .75%, 3.4% respectively for the raw image file size for the first three. Test: manual Bug: 111302946 Change-Id: Ia8fb5696151acad59bb144ea93f2c2ddac962bbd
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.