commit | 7b9fef4a75ef7ea8e402857722d345ac2e88995a | [log] [tgz] |
---|---|---|
author | Martijn Coenen <maco@google.com> | Wed Apr 15 11:38:08 2020 +0200 |
committer | Martijn Coenen <maco@google.com> | Thu Apr 16 12:56:57 2020 +0000 |
tree | bc18526195a7da472b836a31ed0ed3f737b9412d | |
parent | 5afd62fb91a626c02722b7da8d8074d98f8e5759 [diff] |
Rename ro.emulated_storage properties. Whether these are enabled or not is independent of whether storage is emulated or not; instead, use 'external_storage', and add the enabled suffix as per property naming guidelines. Bug: 152170470 Bug: 153525566 Test: N/A Change-Id: Id893ce19025ded1ee1521081f7fc722dfee8e662 Merged-In: Id893ce19025ded1ee1521081f7fc722dfee8e662
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.