commit | 0959fbfd2ea98b0c7e74a89189efbede6ac1b20f | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Mon Apr 13 17:07:13 2020 -0700 |
committer | Steve Muckle <smuckle@google.com> | Mon Apr 20 05:31:15 2020 +0000 |
tree | a2272a52e1a4bc979d48e58c42bcd7bce8978c4b | |
parent | 1e1514a5eff121c3d6da6cd9f7bae28b0862a753 [diff] |
generate multiple boot.img files in aosp_arm64 Generate boot.img variants with different schemes for kernel compression (gzip, lz4, none). The boot image is removed from vbmeta for aosp_arm64 since it is not possible currently to store the hashes of multiple variants of a particular image. The GKI will be verified via VTS anyway. Also remove some emulator-specific stuff from aosp_arm64. Bug: 151094943 Change-Id: I465ea6c98d52e839284d51b246203f6b8dfb5566
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.