| commit | 8caba5e14e5a8875c7e2b28c39dfee79947af763 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Oct 27 03:58:09 2021 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Wed Oct 27 16:56:22 2021 +0900 |
| tree | 8bfae77e0cbe23b60b093a294e932bb25ba97a72 | |
| parent | 0f5a41da56c51be5d2e14926ddbbc323ec2f6c9f [diff] |
Support custom APEX signing tool When an APEX specifies its custom signing tool (custom_sign_tool:), apexkeys.txt contains the info and sign_target_files_apks pass the value to apex_util. For now the Virt APEX has its own custom signing tool (sign_virt_apex), which is added to OTATOOLS. Bug: 193504286 Test: sign_target_files_apks invokes sign_virt_apex Change-Id: Iba845723fe3e18f542963324b9c58cd00914c5ba
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.