| commit | 9b103e49e955a07bac48e74efe5817ec4fe70651 | [log] [tgz] |
|---|---|---|
| author | Andrew Scull <ascull@google.com> | Sun Nov 29 14:04:28 2020 +0000 |
| committer | Andrew Scull <ascull@google.com> | Mon Dec 07 12:31:23 2020 +0000 |
| tree | 2ff5dc1174a9a276e02d413f08e85b7c77e2f55e | |
| parent | 33571ac8dd96b1b467bf00ecf88e72e4cb3625dd [diff] |
Add option include a pvmfw partition
Protected KVM relies on protected VM firmware (pvmfw) to bootstrap the
trust in protected VMs. This firmware is AVB protected and stored in the
pvmfw partition.
Test: build a target with BOARD_PREBUILT_PVMFWIMAGE set, saw the image
included in the product files and used avbtool to check the footer
and vbmeta.img details.
Bug: 171280178
Change-Id: I4d6a1819f307c77ca60c0dd3dff39ee28cece4f6
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.