| commit | 3f6c610206383e94d5a9a63c48abbab052be27d5 | [log] [tgz] |
|---|---|---|
| author | Karsten Tausche <karsten@fairphone.com> | Fri Jul 02 15:38:10 2021 +0200 |
| committer | Karsten Tausche <karsten@fairphone.com> | Fri Aug 04 09:09:10 2023 +0200 |
| tree | 9ae358468f8e13f2b1fa900135b9cd60042d6540 | |
| parent | e71a453dfeb67ab17bb204a08e1834621bb65660 [diff] |
sign_target_files_apks: update ro.build.keys CAF introduces ro.build.keys as build property, see change I4182ba2e297d69ddd203f7e6ef0905e1e7239eaa here and I9f06bd8259613ad6cf93fe990cb27b06f5514937 in system/core. However, it doesn't seem to support signing target files. We keep the release keys out of the build and only sign the target files with them, so we also need to update all related system properties during signing (as recommended and implemented by AOSP). Issue: FP3-A11#54 Issue: FP4-INT#19 Change-Id: Ibca057e95a53b7ad7a4dad9948f93992716a1a96 (cherry picked from commit 25f33842270b71f489d05c740d3fd205f77b881a)
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.