commit | 36fc9a32d7127e2138b7903303d685ee08c7ca2c | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Thu Jun 15 13:20:38 2023 +0900 |
committer | Jiyong Park <jiyong@google.com> | Thu Jun 15 13:20:38 2023 +0900 |
tree | eb0ac8d926952b64e73db8cf73805a1c128d627c | |
parent | 4b47e8a2f3c79735a17e836aa6ab86f9f0b667c3 [diff] |
Move ro.apex.updatable to the system partition The decision to support updatable APEX or not used to be SoC-specific because updatable APEX (aka non-flattened APEX) requires some kernel feature support like loopback device. Kernel was considered as part of BSP then. Therefore, ro.apex.updatable property was in the vendor partition. However, with GKI, kernel is no longer SoC-specific. And most APEXes are installed to the system partition, which means that the decision affects how the system partition is built. Thus, this CL moves the property to the system partition. This enables some partners who have been using flattened APEX to be able to upgrade to non-flattened APEX without having to upgrade the vendor partition. Bug: 281007951 Test: check system/build.prop Change-Id: I81874076862f6047b9daa14518b95adcb5275064
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.