| commit | e555ab18481114f61a603fbe6274b311758af14a | [log] [tgz] |
|---|---|---|
| author | Oleh Cherpak <oleh.cherpak@globallogic.com> | Mon Oct 05 17:04:59 2020 +0300 |
| committer | Oleh Cherpak <oleh.cherpak@globallogic.com> | Tue Oct 20 18:29:35 2020 +0000 |
| tree | 86c84a4db310d9c68e264ea72bf8ef0216513eb8 | |
| parent | 0071b0b56d7c630f4cd823e0b55c1f0e08b96010 [diff] |
sign_target_files_apks: Fix password encrypted keys handle
This patch restores the possibility of using password encrypted
keys for build signing.
Bug: 171221825
Test: 1. Generate password encrypted keys (write non empty passwords):
$ subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
$ mkdir ~/.android-certs
$ for x in releasekey platform shared media; do \
./development/tools/make_key ~/.android-certs/$x \
"$subject"; \
done
2. Create a file with passwords:
Example of passwd file:
[[[ 12345678 ]]] /home/user/.android-certs/releasekey
[[[ 12345678 ]]] /home/user/.android-certs/platform
[[[ 12345678 ]]] /home/user/.android-certs/shared
[[[ 12345678 ]]] /home/user/.android-certs/media
[[[ 12345678 ]]] /home/user/.android-certs/networkstack
3. Tell system where to find passwords:
$ export ANDROID_PW_FILE=/path/to/file/with/passwords
4. Generate a release image:
$ make dist
$ sign_target_files_apks \
-o --default_key_mappings ~/.android-certs \
out/dist/*-target_files-*.zip \
signed-target_files.zip
Signed-off-by: Oleh Cherpak <oleh.cherpak@globallogic.com>
Change-Id: I3e9d5318f69a2c3ac6eec64b36163b6544d49c90
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.