commit | 88648d33c93715ec83b7c16b875fb33b38a539d6 | [log] [tgz] |
---|---|---|
author | Pierre-Clément Tosi <ptosi@google.com> | Fri Sep 24 15:41:13 2021 +0200 |
committer | Pierre-Clément Tosi <ptosi@google.com> | Mon Oct 04 11:37:19 2021 +0200 |
tree | 2e58877b5973d092011b69061e16310460dd8025 | |
parent | b9306ac477d4d2be5cfd079f56b583bb0009e687 [diff] |
Stop assuming that pvmfw.img can only be pre-built Introduce the BOARD_USES_PVMFWIMAGE variable, similarly to all other partitions, and use it where appropriate (in particular, where the soon-to-be incorrect assumption that pvmfw.img could only be a pre-built board image was made). Bug: 199717422 Test: m ${ANDROID_PRODUCT_OUT}/pvmfw.img # with TARGET_PKVM_ENABLED=true Change-Id: I8f4faa78c741d29b473303b521834387dbd48cd1
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.