Google Git
Sign in
android / platform / build / 8c7f820512
commit8c7f820512c0613fa8d473d2c1aab94d828f28fa[log] [tgz]
authorBowgo Tsai <bowgotsai@google.com>Tue Feb 22 14:47:45 2022 +0800
committerBowgo Tsai <bowgotsai@google.com>Tue Feb 22 15:00:22 2022 +0800
tree1387a5c80c4659c3aa5c384ab1cc8ea3788c02ce
parentc25bd3c8a0e0b521f2b9ab9d749320b0a2ee0b6f [diff]
Adding BOOT_OS_VERSION for the AVB prop in a boot.img

Devices using a prebuilt boot.img, e.g., a GKI, will re-sign
the boot.img to append AVB footers. Currently the value of
"com.android.build.boot.os_version" in the AVB footer is set
to the Android platform version. However, the GKI image might
be from another release branch, e.g., using a Android12-5.10
GKI in a Android 13 codebase.

Adding BOOT_OS_VERSION to allow specify the value separately.

Bug: 211364958
Test: make, then `avbtool info_image --image $OUT/boot.img`.
Change-Id: I335cc7b6c5a455d566f364df6a7dae79facc7a87
1 file changed
tree: 1387a5c80c4659c3aa5c384ab1cc8ea3788c02ce
  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. Deprecation.md
  13. envsetup.sh
  14. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. tapasHelp.sh
  22. 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.