| commit | cb1d31c43b7bf66ded40879bd1daf42234215db8 | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Wed Sep 07 10:36:54 2022 +0100 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Fri Sep 09 19:15:30 2022 +0100 |
| tree | 0bd1d8c2f9657a57f0a41e005ea8acf9e4b8ad63 | |
| parent | 085a34b9634ee536a090408e496b3980611c032a [diff] |
core: Drop support for BOARD_PREBUILT_PVMFWIMAGE Remove the variable as it was only used when the prebuilt was device-specific but pvmfw is now part of AOSP. Bug: 237371962 Test: m $(realpath --relative-to=. $ANDROID_PRODUCT_OUT/pvmfw.img) Change-Id: I5b4c1ffd563e3dccf22ee485cb12866355f5bfe0
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.