commit | 3bda0d6992b52ec1d5b1395a1b252e561df55b52 | [log] [tgz] |
---|---|---|
author | Pierre-Clément Tosi <ptosi@google.com> | Tue Sep 21 13:49:35 2021 +0200 |
committer | Pierre-Clément Tosi <ptosi@google.com> | Mon Oct 04 11:56:56 2021 +0200 |
tree | fdc8579eb182c2c4756051b9099fb620c8d2812c | |
parent | fa8193c0e9e3bb3f22a2078744eb95182ebcfd13 [diff] |
Add generic board-agnostic pre-built pvmfw.img Make use of the pvmfw.img-building AOSP framework to provide a common default image instead of requiring boards to necessarily provide their own but allow over-writing it through BOARD_PREBUILT_PVMFWIMAGE, if desired. Note: The Android Virtualization Framework requires the pvmfw partition. Bug: 199717422 Test: m ${ANDROID_PRODUCT_OUT}/pvmfw.img Change-Id: I5e06f08d6e22178e45254b7ab63acd3855d99a38
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.