cddea9b426
The APEX symlink optimization is a build-time trick to save the storage/RAM usage of APEX by replacing some files in APEX with symlinks to the files in the system partition. The optimization however is automatically turned off for 'updatable: true' APEXes because doing the optimization for them will hide the sys-health implication until when the APEXes are built unbundled (i.e. prebuilt) and thus the optimization is impossible. TARGET_FORCE_APEX_SYMLINK_OPTIMIZATION forcibly disables the safety net. When it is set to true, the symlink optimization is done regardless of the 'updatable' property. This is useful for some of the devices like Go where most APEXes (even the 'updatable: true' ones) should be effectively non-updatable. Bug: 175630508 Test: TARGET_FORCE_APEX_SYMLINK_OPTIMIZATION=true m and check that updatable APEXes have symlinks to system libs Change-Id: I261fd4ab2dd8e62ff435306b11168121cbcf662a |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
rbesetup.sh | ||
tapasHelp.sh |
README.md
Android Make Build System
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.