Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / c12ba3b705fe68c522b033eb27511cb7667ad1b0
commitc12ba3b705fe68c522b033eb27511cb7667ad1b0[log] [tgz]
authorCosmin Tanislav <demonsingur@gmail.com>Wed Jul 24 21:52:13 2024 +0300
committerLuK1337 <priv.luk@gmail.com>Sat Oct 19 00:16:02 2024 +0200
treeb6299e5517aaffec3aa402e2e7cfe8b1a9998337
parent98549f6893c3a93057e2d4cdd1015a93e9473b16 [diff]
Don't copy recovery.img to BOOTABLE_IMAGES if it doesn't exist

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
1 file changed
tree: b6299e5517aaffec3aa402e2e7cfe8b1a9998337
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. Usage.txt
README.md

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.