| commit | 3c77151b46eb2d8e030e630a041575f4c5b64c9a | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Wed Jun 30 22:11:09 2021 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Thu Jul 01 16:34:29 2021 +0800 |
| tree | e8e938a2f4d31e027f06e1306b48ee8d5f678d84 | |
| parent | 0427fb4a97ff4abdf4bc370d4ae2b8b5e1825ffe [diff] |
Adding adb_debug.prop into generic_ramdisk.mk After commit I59cd149e0021211b8fd59c44b93bbf18dc8637bf, init_first_stage is no longer installed to the ramdisk when BOARD_USES_RECOVERY_AS_BOOT is True (see b/190974433 for details and init/Android.mk in that commit). adb_debug.prop, which is needed for boot-debug.img, boot-test-harness.img, etc.,will be absent when BOARD_USES_RECOVERY_AS_BOOT is true, because adb_debug.prop is only required by the init_first_stage. Adding adb_debug.prop into generic_ramdisk.mk to include it unconditionally. Bug: 192432810 Test: flash boot-debug.img on a user build, check `adb root` works Change-Id: I234b3430af1b8b09aeb46aef928ca8e16ad452cc
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.