| commit | 615f081bcf0d024ef76501c6f9cf912557f3e7c3 | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Wed Oct 26 16:05:16 2022 +0100 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Wed Oct 26 16:05:16 2022 +0100 |
| tree | 4d07e8c588f56757e92dcf6b274e0c2bc08d8dc9 | |
| parent | aa3b3229717201e2a74a3660f73fcc303a3fcaf8 [diff] |
core: Use pvmfw_embedded_key for INTERNAL_PVMFW_EMBEDDED_AVBKEY Instead of wrongly using the key that was used to sign pvmfw, we should have been using the key that pvmfw will use to verify payloads it receives so fix that. Bug: 255575669 Test: - Change-Id: I68a87a092c1aa4a60f4fbe60c5ddf82c4e34c38a
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.