commit | b225d8c49904562a26718dde796761efbd2ac817 | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Mon Oct 18 18:32:46 2021 +0800 |
committer | Yi-yo Chiang <yochiang@google.com> | Thu Jan 06 06:37:05 2022 +0000 |
tree | 592bdb03e52d140be342808ec50b44cfb18b9ec4 | |
parent | bff997fd1fb51af86e0cc1990e1332449384cbf5 [diff] |
Verbose warning message for PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT I56ed328a9ae70cf49dbd3c6efb5a4a8c54e1b7a7 added a validation check to otatools to check the target_files archive for the existence of userdebug_plat_sepolicy.cil. That check superseded the original PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT product_config.mk check and is more robust because it can handle not only phone GSI but also car/tv GSI (downstream of phone GSI). Modify the check to show a scary wall of text if non-compliance-GSI products tried to set PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT, instead of erroring out immediately. Also add gsi_car_arm64 & gsi_car_x86_64 to the list of eligible GSI product names. After this change, any product can set PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT for development purposes, but only GSI products that specifies `--allow_gsi_debug_sepolicy` during image signing can release sign a product built with PRODUCT_INSTALL_DEBUG_POLICY_TO_SYSTEM_EXT. Bug: 188067818 Test: Presubmit Test: lunch gsi_arm64-userdebug && m nothing # => no warning Change-Id: I34ef49af29c7064bea8924b0070793f1e78256bf
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.