| commit | fd59e543e81be5c384b1c2e40f9023833ab6dc0d | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Tue Sep 17 15:37:49 2019 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Fri Sep 20 12:04:03 2019 +0000 |
| tree | 2d7af25565ba8c42c1bb8219217f57270ca50c7c | |
| parent | 30e613a48de90496dead75f4ca98492b72066dfc [diff] |
Move ro.com.android.dataroaming sysprop to aosp_product.mk
aosp_${device}.mk all have this system property set inside
vendor/build.prop:
ro.com.android.dataroaming=true
so move this common setting into aosp_product.mk
We don't move this to //device/google/${device}/device-${device}.mk
because this property is only used by AOSP builds, so it may cause
issues if we make it a common setting across all device builds.
Bug: 136525499
Bug: 135502030
Test: Compare $ANDROID_PRODUCT_OUT before and after this change
Change-Id: Idd9e235707d9a7fea28fa8c741ad1a4014f71c86
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.