| commit | a9a50cf6e37dbcd73bfed3759e2848cc064af454 | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Tue Jul 14 16:36:53 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Tue Jul 14 17:23:07 2020 -0700 |
| tree | 163ebcd83e073b76d355c05048c817e62f2f82a0 | |
| parent | ce637304a008a63266ee1a07a672137e452275d1 [diff] |
Use apksigner in check_target_files_signatures Some apk files, e.g. Chrome.apk has switched to use v2+ scheme. And the apk file no longer has a META-INF/CERT.RSA. So, the signature parsing script should use apksigner to dump the cert info. Leave the parsing of META-INF/CERT.RSA as a fallback, as some apks fail the `apksigner verify`. The script also switches to store the digest of the cert instead of the raw bytes. Bug: 157735036 Test: run check_target_files_signatures on aosp|signed target-files Change-Id: I910cd1aa91d1e446bef7097871af4171c285685d
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.