Closed ghost closed 8 years ago
We've overridden the normal release target to add our own wrapper around the android signing process. We then call the normal android build process through the target name android_rules.release. You might be able to do the same from the command line.
On Sun, Sep 20, 2015 at 3:17 AM, Boris Kraut notifications@github.com wrote:
Our current setup at f-droid.org handles signing on it's own and doesn't hand that over to the individual gradle or ant build tools. Is there an easy (without tampering with the build files) way to generated unsigned release binaries? Maybe a ant target that I've missed?
— Reply to this email directly or view it on GitHub https://github.com/servalproject/batphone/issues/109.
verdict?
Works for me; $ ant android_rules.release
Our current setup at f-droid.org handles signing on it's own and doesn't hand that over to the individual gradle or ant build tools. Is there an easy (without tampering with the build files) way to generated unsigned release binaries? Maybe a ant target that I've missed?