2929cadb3b
The recovery image already contains a copy of first stage init, so we can boot unconditionally to the recovery image and instruct first stage init whether or not to boot to Android or to recovery. In this case, we need neither the kernel to mount /system as / nor a separate partition for recovery, so this change modifies the build scripts to allow this combination. Bug: 114062208 Test: Boot pixel from recovery to Android with BOARD_USES_RECOVERY_AS_BOOT But without BOARD_BUILD_SYSTEM_ROOT_IMAGE Change-Id: Icd047afb7f22d2724b3bcaca1aa0c837426dcce7 |
||
---|---|---|
core | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.mk | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
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.