| commit | 7073f5a18b528936653cf840894abb4e4934c32e | [log] [tgz] |
|---|---|---|
| author | HZ <thecodehustler@gmail.com> | Thu Oct 06 21:45:42 2022 +0800 |
| committer | LuK1337 <priv.luk@gmail.com> | Sat Oct 19 00:16:02 2024 +0200 |
| tree | 9bbc166db845704873b3a5cdaaae24462bd9eb8d | |
| parent | 5b54cae3a113f03caf9e20e394bae7a6f7395047 [diff] |
Add bluetooth to default key map Previously the key mapping in releasetool/sign_target_files_apks.py is missing the aforementioned key that was introduced in Android 13, so it's writing corrupted signatures in plat_mac_permissions.xml. Test: make target-files-package otatools sign_target_files_apks -o -d <CERT_ROOT> ... Change-Id: If42907cffbd500281876f8f822cbb645583d06ed
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.