| commit | f69346e0a82453a38e8cb2ad3a6fa109967904d3 | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Wed Oct 13 15:16:33 2021 +0900 |
| committer | Inseob Kim <inseob@google.com> | Thu Nov 11 11:19:44 2021 +0000 |
| tree | ffd677ec4e31af6d591d23ced24b1c9a65cc3265 | |
| parent | 9cda3979487d0c72b12684a5594c5c440327fd3e [diff] |
Add fsverity digest manifest fsverity digest manifest stores a map from files to fsverity digests. The manifest is installed as a serialized protobuf file, to a signed apk system/etc/security/fsverity/BuildManifest.apk. Bug: 193113311 Test: build with PRODUCT_SYSTEM_FSVERITY_GENERATE_METADATA := true Change-Id: I55fc10400206b8ce0d5f198faea08fe3930b362c
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.