| commit | 0f5a41da56c51be5d2e14926ddbbc323ec2f6c9f | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Oct 27 03:53:21 2021 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Wed Oct 27 16:56:22 2021 +0900 |
| tree | 20c90c687d136e880c3037110f0de46c4cc63664 | |
| parent | c4b7b34b4b7d8e1f88dd21d2495206e437caa025 [diff] |
sign_apex --sign_tool
A new argument is a custom signing tool for APEX contents. When
specified, apex_util invokes the tool with payload's key and payload
directory.
For now, the Virt APEX has its own custom signing tool (sign_virt_apex)
to re-sign filesystem images in it.
Bug: 193504286
Test: atest releasetools_test
Test: m sign_apex sign_virt_apex
Test: sign_apex --sign_tool sign_virt_apex --payload_key ..
--container_key .. resigned.apex
adb install resigned.apex
reboot & vm run-app
Change-Id: Ic4d369c2ba42a8295044a0a75e054dc8def93208
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.