Add macro to support prebuilt vendor_vboot.img

There are marcos support to link prebuilt images and generate AVB images
in "make"/"make dist" flow. Currently defined marcos only cover boot.img
/init_boot.img/vendor.img and so on, missing the vendor_boot.img.
Appending a marco for prebuilt vendor_boot.img to work like other
prebuilt images.

Test: manual
Build pass in "make" and "make dist" flow and boot up with AVB

Change-Id: I7b296f82e57e8f71a0757d872d35ac27a8d2ecbe
Signed-off-by: chunhui dai <chunhuid@amazon.com>
1 file changed
tree: 6c9fe4b51c227a0dcc80adb02426d6013b525da7
  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.