| commit | a4a53929819df7ac7673c2a5058f631c7fb9110e | [log] [tgz] |
|---|---|---|
| author | LibXZR <i@xzr.moe> | Sat Apr 30 16:29:35 2022 +0800 |
| committer | hmtheboy154 <buingoc67@gmail.com> | Wed Jan 08 12:27:32 2025 -0500 |
| tree | afca2bced453468a0e9eca077b6e249d4321d6cf | |
| parent | 77c3d1042c732b977f7e3179b0061c7a7685812a [diff] |
tools: Let adb secure check depend on "==0" rather than "!=1" We are using PRODUCT_SYSTEM_DEFAULT_PROPERTIES to set `ro.adb.secure` property. But unfortunately this flag only affect system partition, which means in other partitions e.g. vendor and system_ext `ro.adb.secure` stays empty. Thus `persist.sys.usb.config=adb` is unconditionally set in partitions other than system, which lead to adb enabled by default even on user build. Change-Id: I1f8b463b3ec645309369f36014bed556e75ed210 Signed-off-by: LibXZR <i@xzr.moe>
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.