| commit | 408d898a43794ede1214ecae9bd4f66d249fe608 | [log] [tgz] |
|---|---|---|
| author | Hridya Valsaraju <hridya@google.com> | Wed Apr 07 10:37:39 2021 -0700 |
| committer | Hridya Valsaraju <hridya@google.com> | Mon Apr 12 16:34:27 2021 -0700 |
| tree | 36d0f9e82849f6a3f2a0b57b301cd8d164ac3399 | |
| parent | ffa65ba8f05078a1d4ffa1f9961e0e04a50d6ac9 [diff] |
Enforce debugfs restrictions for S launching devices and newer Starting with Android R, debugfs cannot be mounted on production devices. In order to minimize the differences w.r.t debugfs between user and userdebug/eng builds, enforce a set of run-time and build-time restrictions on debugfs access for S launch devices and newer. For non-user builds, debugfs can still be accessed by root and by the dumpstate HAL during bugreport collection. Bug: 184381659 Test: build/boot Change-Id: I2af49acd8a5b3440c6ecbf365ab43cdb33ff897a
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.