| commit | cea6ad1fb022a6c2cc43d2666720807d5f4720c4 | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Thu Jan 30 17:12:05 2020 -0800 |
| committer | Tianjie Xu <xunchang@google.com> | Fri Jan 31 01:37:36 2020 +0000 |
| tree | 69566ea7157b5a6331e04a28ccee30296bd08609 | |
| parent | d0511cfbbbdff60e77d59218be162bf471d8976f [diff] |
Pass signing_args to apexer to repack apex In the build signing environment, we don't necessary have access to the physical private key. And we work around it by passing an extra signing_helper to the avbtool instead of a private key. Since we need to perform signing to add the hashtree footer when rebuilding the apex image. We should propogate the signing_helper to apexer and eventually to avbtool. Bug: 148627666 Test: unit tests pass. Smoke test by pass a public key to apexer and hardcode the private key in signing helper script. Change-Id: I56d57485493a5ba2cbe4c49e493ee9604f68088b
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.