commit | 0a468fe904768240fe011f1c47fa89b3165c265c | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Sat Sep 11 19:31:28 2021 +0800 |
committer | Yi-Yo Chiang <yochiang@google.com> | Fri Sep 17 20:53:56 2021 +0800 |
tree | 5ca75dc5ec26d8e08dabdeb7983babeac43e6a13 | |
parent | 1ab1c2ff9676bd8af9ea8f000193e5bd0d69ca65 [diff] |
Add PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT If this option is set, then an additional copy of the debug policy can be installed to the GSI, and the init-second-stage of GSI could load debug policy from GSI /system_ext when debug-ramdisk is used. Bug: 188067818 Test: Flash RQ2A.201207.001 bramble-user with debug ramdisk & flash gsi_arm64-user from master, device can boot and `adb root` works Change-Id: I9c3dad8bb6c5fa88b16762193446dc7e54f326c8
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.