| commit | 0e06cb0a8b86374a259fd27811e50c0bbb28fbf8 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Fri Mar 22 23:16:58 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Fri Mar 22 23:25:12 2019 -0700 |
| tree | 71627a8a4aae79ff33fcba26289e7e8ea43f66f0 | |
| parent | 5d816d89ebe1b01a4cf49928954adef027cad536 [diff] |
releasetools: Fix alignment issue when signing APEXes.
Previously it was following a wrong order by doing `zipalign` after
calling SignApk, which effectively compromised the signature. This CL
corrects the logic, and follows the same flow as in build system:
- Pack APEX file;
- `zipalign -f 4096`;
- Call SignApk to sign the container with `-a 4096` flag.
Bug: 129148142
Test: Run sign_target_files_apks.py on taimen target_files.zip. Boot the
image after signing.
Change-Id: I91bd3dce4f45c1891c5e122212a699f4808618fa
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.