| commit | a2a5db44663a8dff93f0456034e17848155613f8 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Thu Sep 23 15:46:33 2021 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Thu Sep 23 22:19:52 2021 +0800 |
| tree | 92d6cb02c5f8ac470fcb72f7469da8a47bcdfc0d | |
| parent | 4cf8170fedb3ab38a7b2306f7dffef5d593787f8 [diff] |
Renames boot-debug-*.img in GSI targets Those boot-debug-*.img is used with `repack_bootimg` for a vendor_boot-debug.img in VTS setup. It is not for GKI boot.img release. https://source.android.com/compatibility/vts/vts-on-gsi#repacking Renames boot-debug-*.img to boot-with-debug-ramdisk-*.img to avoid confusion with the official GKI boot.img release. Bug: 200878300 Test: `lunch gsi_arm64-user` then `make bootimage_debug` Change-Id: Ia1f6ba847d5b7409fb7a8534432484d2aa972494
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.