5a05cc117e
If BOARD_USES_RECOVERY_AS_BOOT is set to true, recovery.img is not built. If BOARD_CUSTOM_BOOTIMG is set, INSTALLED_RECOVERYIMAGE_TARGET gets copied to BOOTABLE_IMAGES. If both are set, the following error is produced. acp: missing destination file Since it is possible to have both BOARD_USES_RECOVERY_AS_BOOT and BOARD_CUSTOM_BOOTIMG set, guard the copy operation so that it does not try to copy a missing recovery.img. Change-Id: Iae24e31a586e98955807d213df3dbaa0a2f13bae Signed-off-by: RITEFANG <1721985272@qq.com>
Android Make Build System
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.