| commit | 02426e61186a95b3cdc63bd3b7f4884f20ba9f24 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Wed May 08 20:23:42 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Thu May 09 09:56:55 2019 +0900 |
| tree | 4d29b51d998976f18bd05d4b72a6d3a89058430f | |
| parent | 03aebddf1dd97662f8032526c4cea29f2a8d7e82 [diff] |
Ensure TARGET_FLATTEN_APEX == true when ro.apex.updatable is not set TARGET_FLATTEN_APEX and ro.apex.updatable cannot be independently set. For a device where updating APEXes is not supported, ro.apex.updatable should not be set (or set to false) and TARGET_FLATTEN_APEX should be set to true. For APEX-supporting devices, it is the opposite; ro.apex.updatable == true and TARGET_FLATTEN_APEX is false (or not set). To ensure this relationship, TARGET_FLATTEN_APEX is by default set to true, and overridden to false when updatable_apex.mk is inherited. Bug: 130623080 Test: choosecombo to Pixels 2 and later; get_build_var TARGET_FLATTEN_APEX returns false. choosecombo to the original Pixel and other non-Pixel targets; get_build_var TARGET_FLATTEN_APEX returns true. choosecombo to the cuttlefish; get_build_var TARGET_FLATTEN_APEX returns false Merged-In: Id73a594dd9838457e68e2793122592c11a84fc83 Change-Id: Id73a594dd9838457e68e2793122592c11a84fc83 (cherry picked from commit 18411a42f022099d00d1c0daf13ea7ffdc2b4c36)
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.