commit | f17840d8850c81d055af7832d1a3a27f29d658ca | [log] [tgz] |
---|---|---|
author | Victor Hsieh <victorhsieh@google.com> | Fri Apr 03 15:04:09 2020 -0700 |
committer | Victor Hsieh <victorhsieh@google.com> | Tue Apr 21 15:03:41 2020 -0700 |
tree | e31c359e986e90a4f121b46452528e7a405bdb47 | |
parent | 032c967caf4b8dd45d14184d22f90079c310b4b3 [diff] |
Add fsverity release cert The release cert helps verifying CTS in a release build. Bug: 153112812 Test: build, reboot, see a new key in /proc/keys Change-Id: I6d8f4af6b1b0c023b668e81b7a1c71c7583d93d9 Merged-In: I6d8f4af6b1b0c023b668e81b7a1c71c7583d93d9
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.