Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / e68d922118ba89a3760c4a15f80fdbaf71a3584b
commite68d922118ba89a3760c4a15f80fdbaf71a3584b[log] [tgz]
authorSeungjae Yoo <seungjaeyoo@google.com>Mon Dec 04 13:08:24 2023 +0900
committerSeungjae Yoo <seungjaeyoo@google.com>Tue Dec 05 12:17:46 2023 +0900
tree40638ec336d01e129ab58d14f84f1212c32a66e5
parent2f9162f1cb5c97a4c686b65cae6dd4b17bf49f0d [diff]
Append pubkey of microdroid-vendor into avb prop of vendor_boot

For protected VM in AVF, the public key of microdroid-vendor partition
should be passed via trustable way. However, pvmfw config data is
constructed from ABL. AVB property is needed to pass the public key from
the source code into ABL, determined in the build time.

Bug: 285854379
Test: avbtool info_image --image $ANDROID_PRODUCT_OUT/vendor_boot.img
Change-Id: I024d1d835cccb27feef1164aca30712dbb8a70da
1 file changed
tree: 40638ec336d01e129ab58d14f84f1212c32a66e5
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. cogsetup.sh
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. shell_utils.sh
  23. tapasHelp.sh
  24. 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.