RTsoft Wiki

User Tools

Site Tools

Trace:
proton:android_projects

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
proton:android_projects [2022/04/06 11:05] – sethproton:android_projects [2022/08/01 07:41] (current) – [V3 style] seth
Line 1: Line 1:
-**NEW:**  5/23/2012 - Samples now work with latest versions of Android SDK (**YOU MUST HAVE THE LATEST SDK TOOLS NOW!**) , NDK and Ant, and use new build setup with a java pre-processing step 
- 
 ==== Intro ==== ==== Intro ====
  
Line 11: Line 9:
 V3 style:  Using Android Studio/Gradle, a very normal looking project, nothing weird about it really. V3 style:  Using Android Studio/Gradle, a very normal looking project, nothing weird about it really.
  
-==== V2 style (oudated!) ====+==== V2 style (outdated!) ====
  
 At some point in history it came apparent that on Android some Java classes (provided by Proton) need to be in specific packages. And these packages change from project to another. Hence it was necessary to introduce a way to get (almost) the same source files to different directories (and thus to different packages) in different projects. The source files also needed small modifications in the code, for example the package name needs to be specified in the source. At some point in history it came apparent that on Android some Java classes (provided by Proton) need to be in specific packages. And these packages change from project to another. Hence it was necessary to introduce a way to get (almost) the same source files to different directories (and thus to different packages) in different projects. The source files also needed small modifications in the code, for example the package name needs to be specified in the source.
Line 33: Line 31:
  
 After a few more years, Seth created an Android Studio/Gradle based build.  The preprocessor is no longer used and the build system is simplified quite a bit, you just change the package id in a single place (AndroidGradle/local.properties) and edit a CMakeLists.txt file to set which C/C++ files compile.  Android Studio can load the project and run/debug on devices or emulated devices very easily. After a few more years, Seth created an Android Studio/Gradle based build.  The preprocessor is no longer used and the build system is simplified quite a bit, you just change the package id in a single place (AndroidGradle/local.properties) and edit a CMakeLists.txt file to set which C/C++ files compile.  Android Studio can load the project and run/debug on devices or emulated devices very easily.
 +
 +Android Studio handles installing Gradle/NDK/etc by itself, much simpler than before.
 +
 +Note:  I've ripped out built in support (on the Java side) for In App Billing, Chartbooost/Tapjoy/Etc as I assume they don't work anymore anyway as I haven't used them for years.
 +
 +It is possible to use third party libraries the "gradle way" or directly by linking files, I do this in Dink Smallwood HD android for FMOD support.
 +
 +IMPORTANT NOTE:  The package ID set in App.cpp MUST match the one set in local.properties.  Those are the only two places you need to worry about it.  The RTAndroidApp name you see everywhere stays that way and shouldn't be changed. (it's used for internal bindings but won't affect the real build's package id etc)
  
 ==== Building ==== ==== Building ====
proton/android_projects.1649243139.txt.gz · Last modified: 2022/04/06 11:05 by seth