| commit | 6a68367e6ee460bab5edb96c20f80ce14999b5de | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Fri Feb 14 19:00:15 2020 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Tue Feb 18 13:46:17 2020 +0800 |
| tree | a945d9b1e6371cf64d17ec9264a2348bc809c8c8 | |
| parent | ae541174cc89140888660fdb2ed2aa8ea33a9533 [diff] |
Adding vendor_boot-debug.img Commit I30137c3caef91805d9143d404e5e4d06c0fccc30 adds boot-debug.img to allow adb root with an user build GSI image. https://source.android.com/compatibility/vts/vts-on-gsi Another commit I5b005097b73f59857c3a2f92d693b3e67ee8424e adds vendor_boot.img to pair with a generic kernel image, the GKI boot.img. To allow adb root for devices using a GKI, vendor_boot-debug.img is introduced. The image combination used in VTS will be: Old devices without GKI: GSI system.img + boot-debug.img + vendor.img, etc. New devices with GKI: GSI system.img + GKI boot.img + vendor_boot-debug.img + vendor.img, etc. Note that boot-debug.img still can be used on new devices for non-compliance scenario. Bug: 147849477 Test: lunch aosp_cf_x86_64_phone-userdebug; make vendorbootimage_debug Test: `make dist`, checks that both vendor_boot-debug.img and vendor-ramdisk-debug.cpio.gz are in $OUT/ and out/dist. Test: `make dist`, checks that installed-files-vendor-ramdisk-debug.{json,txt} are in $OUT/ and out/dist. Change-Id: I66b662d8b1e5c619ed7bb81e40233fe9df363b27
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.