commit | 45b83a442feaafd07b3d214549f4d67ef89ab411 | [log] [tgz] |
---|---|---|
author | Bartłomiej Grzesik <bgrzesik@google.com> | Tue Jan 21 13:27:07 2025 +0100 |
committer | Bartłomiej Grzesik <bgrzesik@google.com> | Wed Jan 22 12:05:24 2025 +0100 |
tree | bcf2cd4618ec0de7aa5b24c435a0e203c4a0f924 | |
parent | fbcc6337c78b3c486d085d75b277647dc72c352d [diff] |
Temporarily enable use pvmfw prebuilts as fallback This change add a temporary method of delivering pvmfw for x86_64. If pvmfw building is not available (effectively on target other then aarch64) check for prebuilt and if available use it instead. The prebuilt is provided using three new `PRODUCT_PVMFW_IMAGE_PREBUILT`, `PRODUCT_PVMFW_BIN_PREBUILT` and `PRODUCT_PVMFW_EMBEDDED_AVBKEY_PREBUILT`, make variables. One for providing the module with signed pvmfw image, one for raw pvmfw binary and one for specifing the embedded avb key present in the prebuilt image. If `PRODUCT_PVMFW_EMBEDDED_AVBKEY_PREBUILT` is absent it's assumed that prebuilt image has default AOSP key embedded in it. Bug: 391159299 Test: m Change-Id: If4dfb9099d000ac44cda2fd9ccd0892767b4f066
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.