| commit | 8407cf265bc41bac790afa457ac3c94c867f9413 | [log] [tgz] |
|---|---|---|
| author | Danny Lin <danny@kdrag0n.dev> | Sat Nov 07 23:40:39 2020 -0800 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Sep 18 06:04:33 2021 -0400 |
| tree | da536d7265f50319d022dc8e391ddd9079988821 | |
| parent | 259e00b69c96028e1e67344f7c5f82c39e2225c9 [diff] |
build: Add support for faking platform security patch level [1/2] SafetyNet will fail if the fake build fingerprints don't match the platform security patch level, which is a problem for devices that are no longer supported by the manufacturer. To fix this issue, allow legacy products to define a fake security patch level from their last official update and set the standard patch level property to that. The real patch level is moved to another custom property that is shown to the user, e.g. in Settings -> About. Note that this requires the "core: Use real security patch level property" commit in frameworks/base for users to see the correct patch level in Settings. Change-Id: Id09e1b52697e6791987e388551e6f7a6558775ba
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.