| commit | 5c40c7166f38f0cad12a823ff73289d8a0ac20a4 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Tue Oct 08 10:22:19 2019 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Tue Oct 08 10:22:13 2019 +0000 |
| tree | bbf5bdb5749536770b41e311e4c2cd0588178dc9 | |
| parent | 7e49064030c7087e80f6addad61546714cab6a98 [diff] |
Adding boot-test-harness.img In commit I30137c3caef91805d9143d404e5e4d06c0fccc30, we added a boot-debug.img to allow adb root when using an user build GSI image. However, to run automated tests, it requires additional properties, which are not needed for GSI compliance: ro.audio.silent=1 ro.test_harness=1 This CL adds an additional boot-test-harness.img for automated tests, and keeps the original boot-debug.img for GSI compliance. Note: boot-test-harness.img won't be built by default, it needs explicit `make bootimage_test_harness`. Bug: 140036184 Test: `m bootimage_test_harness`, flashes boot-test-harness.img and checks adb root works and test harness props are set. Test: `m bootimage_test_harness dist -j32`, checks both boot-test-harness.img and ramdisk-test-harness.img are under ./out/dist/. Test: `system/tools/mkbootimg/unpack_bootimg.py --boot_img $OUT/boot-test-harness.img --out ramdisk-test-harness`, checks the extracted out/ramdisk is as expected Test: Run `gunzip -c ramdisk | cpio -idm` for the ramdisk extracted from $OUT/boot-test-harness.img and $OUT/boot-debug.img, respectively. Then compare the root dirs of both, e.g., `diff -rq --no-dereference ./ramdisk-test-harness ./ramdisk-debug` Test: `m ramdisk_test_harness-nodeps` and `m bootimage_test_harness-nodeps` Change-Id: Iadea0b5c933c3b7fa10dcf3d9e85596916b3333d
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.