| commit | 6b79c9b769c33e6998130771a66ee850f5564cf1 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Fri May 18 20:16:51 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Thu May 24 19:03:25 2018 +0900 |
| tree | c81060787d0d1de8ea22043fdca1772a1184eff0 | |
| parent | bd842d0b6491bd5194e78fe16fdc03bccd599082 [diff] |
Temporarily whitelisting system domains writing vendor props system properties must not be used as a communication channel in between system and vendor processes. However, there has been no enforcement on this: system process could write system properties that are owned and read by vendor processes and vice versa. Such communication should be done over hwbinder and should be formally specified in HIDL. Until we finish migrating the existing use cases of sysprops to HIDL, whitelisting them in system_writes_vendor_properties_violators so that the violators are clearly tracked. These violators are allowed only for P, but not for Q. Bug: 78598545 Test: m -j selinux_policy when choosecombo'ed to aosp_arm64 Merged-In: I8f66aa20bb2d926cf517d40c93f4300c4d16b04b Change-Id: I8f66aa20bb2d926cf517d40c93f4300c4d16b04b (cherry picked from commit bb1432b61bab1b5a5286cad273ddf81af4372988)
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.