commit | 610286a88f49f72ddf1717ba587b476afcceaeca | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Fri Apr 23 11:31:32 2021 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Sat Apr 24 08:55:02 2021 +0800 |
tree | 0c92b16018421aa1141bb28e5af5b591c5c86e09 | |
parent | 85c91dcee9261d78b890617282b4d05c01ded12f [diff] |
Moving debug ramdisk resources under / of the ramdisk Currently the debug ramdisk resources might be under / or /first_stage_ramdisk of the ramdisk, and is determined by some BOARD variables, e.g., BOARD_USES_RECOVERY_AS_BOOT, BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT, etc. To make a generic boot-debug.img that can work on both devices, let's move the debug resources always under / of the ramdisk. Bug: 186082603 Test: boot a device with boot-debug.img Test: boot a device with vendor_boot-debug.img Change-Id: I55dc8ff322f6b97e2d6dc1a4ee5935e863f2f835
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.