| commit | 3871f0fc612187e00cbd27ee16d7af8a164017fc | [log] [tgz] |
|---|---|---|
| author | Tom Cherry <tomcherry@google.com> | Tue Nov 06 14:23:44 2018 -0800 |
| committer | Tom Cherry <tomcherry@google.com> | Wed Nov 28 08:53:38 2018 -0800 |
| tree | 38c47a6d02aa822d2262bd3176a4ba705733bb6f | |
| parent | 638ca85aec32fa3d4a41589f5397a4b2be0a0c84 [diff] |
Remove copying of TARGET_OUT_RAMDISK to recovery image This was only needed for pushing first stage init to the recovery image. This isn't actually needed however, as the recovery image can be fully shared and can run full init as long as there is a symlink from /init to /system/bin/init, so that is added instead. Bug: 80395578 Test: boot to recovery via this symlink Change-Id: I8910543525a841401b209bfd98af30c5a0dc2688
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.