commit | 0013f55ef4768fdb996894e8d08aa8222467831b | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 20 17:59:52 2019 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Mon Apr 22 21:50:07 2019 +0800 |
tree | a665d2512de5b43561c7662dccdaa781f8737d90 | |
parent | 967105ada9592416210453149cea964f4ca81e58 [diff] |
Adding boot-debug.img and ramdisk-debug.img The two new debugging images adds additional files based on boot.img and ramdisk.img/ramdisk-recovery.img, respectively. File /force_debuggable is to trigger special logic in /init to load an userdebug version of sepolicy and an additional property file from this ramdisk to allow adb root, if the device is unlocked. It's intentional to skip signing for boot-debug.img, as it can only be used if the device is unlocked, where verification error is allowed. Those debugging images allows adb root on user build system.img, vendor.img, product.img, etc. This can facilitate more automated testings on user builds and is helpful to narrow down the delta between what's being tested v.s. what's being shipped. Bug: 126493225 Test: `make dist`, checks both boot-debug.img and ramdisk-debug.img are in $OUT/ and out/dist. Test: `make dist`, checks installed-files-ramdisk-debug.{json,txt} are in out/dist. Test: `system/core/mkbootimg/unpack_bootimg.py --boot_img $OUT/boot-debug.img`, checks the extracted out/ramdisk is as expected Test: Run `gunzip -c ramdisk | cpio -idm` for the ramdisk extracted from $OUT/boot-debug.img and $OUT/boot.img, respectively. Then compare the root dirs of both, e.g., `diff -rq --no-dereference ./ramdisk ./ramdisk-debug` Test: `make ramdisk_debug-nodeps` and `make bootimage_debug-nodeps` Change-Id: I30137c3caef91805d9143d404e5e4d06c0fccc30
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.