| commit | 6d9e3da5f9399f9041c2356080c36b5cb8576166 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Mar 26 12:59:25 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Tue Mar 26 13:05:46 2019 -0700 |
| tree | 70e759dbb51d7ab34bce605fb6caa932bd3fab2a | |
| parent | 072795054a4284924067c5e7e9fa1ca56cb9598a [diff] |
releasetools: Remove the sanity check on APEX payload key names.
Unlike container keys/certs, we'll always carry full names for APEX
payload signing keys.
Test: Run sign_target_files_apks.py on a target_files.zip with
mismatching payload signing keys (e.g. shim apexes).
Test: `python -m unittest test_sign_target_files_apks`
Change-Id: Ifa329478f43b4f5ae665821564dbc14af7841330
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.