| commit | 8f52a568f07fca12a3d2d3275e6de5948f0add90 | [log] [tgz] |
|---|---|---|
| author | Will McVicker <willmcvicker@google.com> | Fri Dec 04 11:05:00 2020 -0800 |
| committer | Will McVicker <willmcvicker@google.com> | Fri Dec 04 11:08:32 2020 -0800 |
| tree | b5de2eaa7276ea08c5e1de7b1256229d163ab6b7 | |
| parent | ad4dae71cf5daf8c93ce0850fe198692d8223396 [diff] |
Enable debug ramdisk for vendor_boot with recovery The debug vendor boot image needs to include the debug ramdisk in order to retain adb root. So make sure this still happens when recovery is moved to the the vendor boot image. Bug: 172510680 Test: verify adb root when using vendor_boot-debug.img Change-Id: I20fe27635dd33e4d8a59e873e704891de223204b
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.