| commit | e077cf764fad5fdff8604c99d25278c621581279 | [log] [tgz] |
|---|---|---|
| author | Andrew Scull <ascull@google.com> | Thu Feb 18 10:27:29 2021 +0000 |
| committer | Andrew Scull <ascull@google.com> | Fri Feb 19 13:07:32 2021 +0000 |
| tree | def0c30458a0eaa1709fdc90fc4492b0c9659a51 | |
| parent | e484f03f0d33d37b980c4f9d396f5966ca232d6e [diff] |
Add pvmfw partition to target files The pvmfw is included in an `m` build but not in the distribution files. Apply the same treatment as the dtbo partition to copy the pvmfw partition to dist/ since, similar to the dtbo image, the pvmfw image is generally provided as a prebuilt image. Test: make dist Bug: 174457787 Change-Id: I6f42517ba42db92e90048d1236d7255ccbd73f73
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.