640544bd96
Starting from Android 10, the system.img layout consists of $TARGET_SYSTEM_OUT and $TARGET_ROOT_OUT, and is mounted by the init as root. That is, system.img is always created as if BOARD_BUILD_SYSTEM_ROOT_IMAGE was set. https://source.android.com/devices/bootloader/partitions/system-as-root The previous concern is that there might be compatibility issues between the ramdisk contained in boot.img with a newer system.img. But this is no longer an issue after we always mount the system.img as root. Bug: 187157581 Test: Tree Hugger Change-Id: I4537e6ce6fb39b4b86caac82a13716abf515ffd6 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.bp | ||
banchanHelp.sh | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
METADATA | ||
navbar.md | ||
OWNERS | ||
PREUPLOAD.cfg | ||
rbesetup.sh | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
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.