Establishing a Build Environment - Android NDK Game Development - page 28

Getting ready
A detailed explanation of the signing procedure on Android is given in the developer manual at
http://developer.android.com/tools/publishing/app-signing.html . We will
focus on the signing from the command line and automating the entire process via batch iles.
How to do it...
First of all, we need to rebuild the project and create a release version of the .apk package.
Let's do it with our App2 project:
>ndk-build -B
>ant release
You should see a lot of text output from Ant , which ends with something like the following
command:
-release-nosign:
[echo] No key.store and key.alias properties found in build.properties.
[echo] Please sign App2\bin\App2-release-unsigned.apk manually
[echo] and run zipalign from the Android SDK tools.
Let us generate a self-signed release key using keytool from the JDK through the following
command:
>keytool -genkey -v -keystore my-release-key.keystore -alias alias_name
-keyalg RSA -keysize 2048 -validity 10000
Fill out all the ields necessary for the key, as in the following command:
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: Sergey Kosarevsky
What is the name of your organizational unit?
[Unknown]: SD
What is the name of your organization?
[Unknown]: Linderdaum
What is the name of your City or Locality?
[Unknown]: St.Petersburg
What is the name of your State or Province?
[Unknown]: Kolpino