| commit | 9c8f6eb7e1a854db6420e13d3f4c63d058389826 | [log] [tgz] |
|---|---|---|
| author | Jose Galmes <jgalmes@google.com> | Wed Jul 21 09:34:08 2021 -0700 |
| committer | Jose Galmes <jgalmes@google.com> | Thu Jul 22 13:39:10 2021 -0700 |
| tree | 6334f064151849425b3405de4d7e09ea5b6750cb | |
| parent | da7ca70cd0dd074e2483242ffaf7f6c3c7ab939d [diff] |
Support for dexopt postprocessing in merge_target_files. When using the VSDK, dexopt is not applied during the vendor build. To avoid a first-boot time regression, dexopt is applied during the merge stage, by running dexopt on the vendor apps and rebuilding the vendor image. Bug: 188179859 Test: Tested in keystone with VSDK target Change-Id: Ie8e2d0a82850a2901fa6f250433bcbb43f0a97f2
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.