|
25.
|
|
|
Install Apache Ant.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:85
|
|
26.
|
|
|
Install the Android SDK.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:86
|
|
27.
|
|
|
Use the Android SDK to install the appropriate development packages.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:87
|
|
28.
|
|
|
Create a signing key that will be used to sign packages that are placed on the market (android.keystore: this will be generated in the RAPT directory).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:89
|
|
29.
|
|
|
This step requires Internet access.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:93
|
|
30.
|
|
|
To perform this step, choose "Install SDK & Create Keys" from the Android screen in the Ren'Py Launcher.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:95
|
|
31.
|
|
|
RAPT will report on what it's doing. It will also prompt you with warnings about licenses, and ask if you want it to generate a key.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:98
|
|
32.
|
|
|
The key generated by RAPT is created with a standard passphrase. You should really use keytool to generate your own signing keys.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:103
|
|
33.
|
|
|
http://docs.oracle.com/javase/1.3/docs/tooldocs/win32/keytool.html
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:107
|
|
34.
|
|
|
At the very least, you should keep the android.keystore file in a safe place. You should also back it up, because without the key, you won't be able to upload the generated applications.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/android-packaging.rst:109
|