Fix dependency issue for boot_ota_16k.zip

The dependency list and rule body of build rules are parsed
at different stages. This caused a problem, the dependency list is
parsed earlier, at which time INSTALLED_BOOTIMAGE_TARGET isn't
defined yet. But rule-body is parsed at a later time, when
INSTALLED_BOOTIMAGE_TARGET is already defined. This causes
non-deterministic build failures, as boot_ota_16k.zip uses
boot.img, but didn't list boot.img in dependency list. Build fails
if boot.img gets built after boot_ota_16k.zip. To mitigate:

1. Move boot_ota_16k after where INSTALLED_BOOTIMAGE_TARGET is defined
2. Use rule-local variables, this ensures that variables in rule-body
   are evaluated at the same stage as dependency list.

Test: m insatllclean; m boototapackage_16k
Bug: 397445008

Change-Id: Ia1f31d093700ea7152a533586bebe1d81f730b27
1 file changed
tree: ee0ef3c5ac55df5f8dc4de2e5d1afdfb71b21b48
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  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.