| commit | 39259ec1a47a5f710660966fdb691e399a84dd55 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Mon Feb 07 15:56:53 2022 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Mon Feb 07 15:56:53 2022 +0900 |
| tree | da0f2495209cb5eace96dc27cfd5e76194b9f3d9 | |
| parent | fb9ec40e652cb47e8cd28d2c6a882fb7bd438421 [diff] |
A custom APEX signing tool with --signing_args apex_utils.SignApex() has `signing_args` argument which is supposed to be passed to avbtool to set `--signing_helper` or `--signing_helper_with_files`. A custom APEX signing tool which relies on avbtool's signing should pass the same arguments when signing_args is set. This change passes signing_args verbatim to the custom APEX signing tool via --signing_args argument. Bug: 216971834 Test: tbd Change-Id: I8aaec9440c4536e11e1e4a1dd4ae5f4fe32d4f23
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.