README-android.txt
changeset 7793 6463a850229d
parent 7501 b27825bb5879
child 7804 1f85fb33694b
     1.1 --- a/README-android.txt	Mon Oct 07 14:16:38 2013 -0700
     1.2 +++ b/README-android.txt	Wed Oct 09 10:29:01 2013 -0300
     1.3 @@ -38,7 +38,33 @@
     1.4   Building an app
     1.5  ================================================================================
     1.6  
     1.7 -Instructions:
     1.8 +For simple projects you can use the script located at build-scripts/androidbuild.sh
     1.9 +
    1.10 +There's two ways of using it:
    1.11 +
    1.12 +androidbuild.sh com.yourcompany.yourapp < sources.list
    1.13 +androidbuild.sh com.yourcompany.yourapp source1.c source2.c ...sourceN.c
    1.14 +
    1.15 +sources.list should be a text file with a source file name in each line
    1.16 +Filenames should be specified relative to the current directory, for example if
    1.17 +you are in the build-scripts directory and want to create the testgles.c test, you'll
    1.18 +run:
    1.19 +    
    1.20 +./androidbuild.sh org.libsdl.testgles ../test/testgles.c
    1.21 +
    1.22 +One limitation of this script is that all sources provided will be aggregated into
    1.23 +a single directory, thus all your source files should have a unique name.
    1.24 +
    1.25 +Once the project is complete the script will tell you where the debug APK is located.
    1.26 +If you want to create a signed release APK, you can use the project created by this
    1.27 +utility to generate it.
    1.28 +
    1.29 +Finally, a word of caution: re running androidbuild.sh wipes any changes you may have
    1.30 +done in the build directory for the app!
    1.31 +
    1.32 +
    1.33 +For more complex projects, follow these instructions:
    1.34 +    
    1.35  1. Copy the android-project directory wherever you want to keep your projects
    1.36     and rename it to the name of your project.
    1.37  2. Move or symlink this SDL directory into the <project>/jni directory