bb9699c2e1
General recommendation is to avoid read-only properties, and instead control "read-onlines" by only allowing init/vendor_init to set the property. Since ro.init.userspace_reboot.is_supported was added in this release, and nobody outside of the platform is querying it directly, it should be fine to simply rename it. Test: adb shell getprop init.userspace_reboot.is_supported Test: atest CtsUserspaceRebootHostSideTestCases Bug: 152803929 Change-Id: Ie3604b315a5d2a846037064ad9a29258f2cad9d0 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Changes.md | ||
| CleanSpec.mk | ||
| Deprecation.md | ||
| OWNERS | ||
| README.md | ||
| Usage.txt | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| rbesetup.sh | ||
| tapasHelp.sh | ||
README.md
Android Make Build System
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.