commit | b39ec7084af54dcab5f56d275363e013df959c31 | [log] [tgz] |
---|---|---|
author | Hridya Valsaraju <hridya@google.com> | Wed Mar 31 21:28:02 2021 -0700 |
committer | Hridya Valsaraju <hridya@google.com> | Wed Apr 07 16:47:59 2021 -0700 |
tree | 019e9fdf390bda0a8892013c7d59c557224f512c | |
parent | bacb3ebb2afa33d86a0ab00c7cc0b9a64140024c [diff] |
Add a build flag to turn on debugfs restrictions Starting with Android R launched devices, debugfs cannot be mounted in production builds. In order to avoid accidental debugfs dependencies from creeping in during development with userdebug/eng builds, this patch introduces a build flag that can be set by vendors to enforce additional debugfs restrictions for userdebug/eng builds. The same flag will be used to enable sepolicy neverallow statements to prevent new permissions added for debugfs access. Bug: 184381659 Test: make with/without PRODUCT_SET_DEBUGFS_RESTRICTIONS Change-Id: I9aff974da7ddce9bf1a7ec54153b161527b12062
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.