commit | 65672df61f1ce5a1c458313daff4ec45360594d7 | [log] [tgz] |
---|---|---|
author | Lingfeng Guan <lguan@fb.com> | Thu Nov 11 21:31:42 2021 -0800 |
committer | Lingfeng Guan <lguan@fb.com> | Tue Nov 23 12:02:16 2021 -0800 |
tree | b80bf3de91dff50522aebdbe05f6d0aedb4729ab | |
parent | 8e7cdf65d15101201c28230e09231aaae441cee2 [diff] |
SignApk - use existing password mechanism when using keystore Summary: In my last diff, I've added mechanism to load private key from keystore. However, that mechanism will reveal password as part of the java param. This diff tries to use existing ANDROID_PW_FILE mechanism to support password for keystore private keys (through stdin) This diff also fix a null pointer bug in the existing password handling Test: This diff has been tested locally, and could sign correctly with our keystore with or without password Tags: Change-Id: Ie291ea8702a3b4d270b0f8689b023c3f290980a7
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.