| commit | 49968aa1379e669791173e54dab488975fe541d0 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Mon Nov 09 11:52:52 2020 -0800 |
| committer | Yifan Hong <elsk@google.com> | Tue Nov 10 12:55:40 2020 -0800 |
| tree | bd3b99b4bec039283975083a74383868aa1695c7 | |
| parent | 4cecc437962f947584d298db16df2392b88c2890 [diff] |
aosp_arm64 Copy boot image from $OUT to target files If BOARD_COPY_BOOT_IMAGE_TO_TARGET_FILES is defined, in target files, instead of rebuilding the boot image, copy the boot image already built in $OUT to target files package directly so that they are the same package. Define BOARD_COPY_BOOT_IMAGE_TO_TARGET_FILES for aosp_arm64. The GKI APEX is built using the boot image in $OUT. If the boot image in $OUT is different from the boot image in target files, aka the generic boot image we release, the GKI APEX we built is invalid. If another device needs to copy $OUT/boot.img to target files, it can define BOARD_COPY_BOOT_IMAGE_TO_TARGET_FILES. Fixes: 172682114 Test: lunch aosp_arm64 && Change-Id: I10fc7a5aa36e976dbeaf25434239687455bba061
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.