core/Makefile: Make PACK_DESKTOP_{RECOVERY,UPDATE}_IMAGE into product variable

Make the PACK_DESKTOP_UPDATE_IMAGE and PACK_DESKTOP_RECOVERY_IMAGE
variables into product variables PRODUCT_BUILD_DESKTOP_UPDATE_IMAGE and
PRODUCT_BUILD_DESKTOP_RECOVERY_IMAGE so that board specific mk files can
override the value of these variables. The original variables can only
be appended to or overridden with 'override' because we use
'inherit-product'. The use of 'inherit-product' causes the test in this
Makefile to always succeed because the variables are set to 'true' by
default. The only other way to reset these variables seems to be to use
'override <var> = ' in the board's product mk file, which isn't
preferred vs. using a product variable.

Bug: 368171802
Test: m pack-update-image; \
      m pack-recovery-image
Change-Id: Iba3bc8bf1715785662260ad7dfc0927cb3e52477
3 files changed
tree: 5060bdf9f6ff3188606c17c0f94be2221e563f27
  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. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. navbar.md
  19. OWNERS
  20. PREUPLOAD.cfg
  21. rbesetup.sh
  22. README.md
  23. shell_utils.sh
  24. tapasHelp.sh
  25. 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.