ac3c65b7bb
Only common files can reside in system partition, other files should be moved to the newly added system_ext partition. Note that for GSI, it will be a single system.img that includes the contents of product and system_ext partitions, under /system/product and /system/system_ext, respectively. After moving skip_mount.cfg to system_ext partition, it also needs a symlink file under system partition: /system/etc/init/config -> /system/system_ext/etc/init/config This allows Q-launched first-stage init (in /boot partition) continue to use the same path when new GSI image is used. Bug: 138281441 Test: build aosp_arm64-userdebug and boot it on crosshatch Test: rm -rf out && build/soong/soong_ui.bash --make-mode \ TARGET_PRODUCT=aosp_arm64 TARGET_BUILD_VARIANT=userdebug droid Change-Id: Iae9f5fb688f49497563864eb882d5f0ae33c744a |
||
---|---|---|
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 | ||
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.