| commit | 8b266f16a90d072dc47415b9332782a0a86292a4 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Jun 22 19:42:59 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue Jun 30 18:44:11 2020 +0900 |
| tree | 8fa06763622537711ad20c5b5551641ff31f751e | |
| parent | d721e870bcc3caf2219adaa4716a3193d3c479d0 [diff] |
Don't inherit tablet-dalvik-heap for GSI and emulator GSI and emulator should not be specialized for tablet. This is also to avoid the expected sysprop conflict after I9c073a21c8257987cf2378012cadaeeeb698a4fb gets in. With the change, duplicate assignments of a sysprop is prohibited. We currently have the duplication due to the following hierarchy chain: aosp_arm64.mk -> emulator_vendor.mk -> goldfish/vendor.mk -> phone-xhdpi-2048-dalvik-heap.mk -> generic_arm64/device.mk -> tablet-dalvik-heap.mk Many of the dalvik.vm.* properties are duplicated between phone-*- dalvik-heap.mk and tablet-dalvik-heap.mk files. Bug: 117892318 Bug: 158735147 Test: atest --host post_process_prop_unittest Exempt-From-Owner-Approval: cherry-pick from master Merged-In: I4d1e2f819fe688a4a85e58387b6af58d603399d3 (cherry picked from commit 9f2f6dd9c9a48b526742a3ca8e21328ac3355b9f) Change-Id: I4d1e2f819fe688a4a85e58387b6af58d603399d3
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.