| commit | 067492988aa84522f54f0a57d0b6fc2530bbe18a | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Mon Dec 13 15:41:48 2021 +0900 |
| committer | Inseob Kim <inseob@google.com> | Wed Dec 15 09:41:39 2021 +0900 |
| tree | bc30929f5d8fcac9ccdbbf0ca509d89c79d1cc00 | |
| parent | 2d0349334144e69597d63ad62e21a267bc1f31ce [diff] |
fsverity_metadata: Support PEM key When we have a PEM key, we don't need the process converting a DER key to PEM format, but we just need to use the PEM key as-is. Bug: 205987437 Test: build and manual test Change-Id: I6f61a9088efc0f7193737d3c33b8cfde399b2b6f
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.