Differences

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

--- proton:android_setup [2012/08/02 01:08] – jake
+++ proton:android_setup [2017/05/22 08:33] (current) – seth
@@ Line 2: / Line 2: @@
 ====Compiling for Android from Windows====
-**NEW:**  3/12/2012 - Proton no longer requires Cygwin to be install to compile android apps on Windows!
+** NOTE: ** 5/22/2017:  I updated to the latest NDK (r14b 64bit) and it works fine, C++11 now supported
+**NOTE:**  6/19/2013 - Proton has been updated to work with the latest Android platform tools (17), SDK tools (22.0.1) and the latest NDK. (r8e)  If your old proton project won't compile, steal the android/build.xml from a proton example and replace your old one.  (And edit the top as need..)
 Originally the Android platform was crippled by requiring all "app" code to be written in Java.
@@ Line 20: / Line 23: @@
 The C++ "glue" code for Android is located in /shared/android and the .Java parts are in /shared/android/src.  These are shared between all applications so be careful if you touch them.
-** Side Note **: There is actually an even newer way to do NDK now - something called a NativeActivity where you can use 100% C++.  Except you can't, because things like IAP and Tapjoy integration would still be in Java so I assume more ugly bridging would be required.. also it requires Android 2.3+ (boo, hiss), but I plan to do an android target supporting this eventually, especially since it seems to be the only way to fully support the xperia play gamepad controls. -Seth
+** Side Note **: There is actually an even newer way to do NDK now - something called a NativeActivity where you can use 100% C++.  Except you can't, because things like IAP and Tapjoy integration would still be in Java so I assume more ugly bridging would be required.. also it requires Android 2.3+, but I plan to do an android target supporting this eventually, especially since it seems to be the only way to fully support the xperia play analog sticks. -Seth
 ====Prerequisites====
@@ Line 35: / Line 38: @@
 Important note:  For all this stuff, try to choose a custom install path WITHOUT spaces in it.  There, I just saved you like 40 minutes of diagnosing vague errors that will happen later.  No charge, friend!
-  * Install the [[http://developer.android.com/sdk/index.html|Android SDK]] - use the Windows exe version so it will also prompt you to install the Java SE JDK which will be needed as well. NOTE - you'll need to install the 32bit version of the Java JDK, NOT the 64 bit, since the android SDK install process won't recognise the 64 bit version. Also note, the advice about using a custom install path applies as much for the Java JDK as it does for everything else. If you install Java to Program Files, ANT will complain about this later (since Ant sits on top of Java).
+  * Install the [[http://developer.android.com/sdk/index.html|Android SDK]] - use the Windows exe version so it will also prompt you to install the Java SE JDK which will be needed as well. NOTE - you'll need to install the 32bit version of the Java JDK, NOT the 64 bit, since the android SDK install process won't recognize the 64 bit version. Also note, the advice about using a custom install path applies as much for the Java JDK as it does for everything else. If you install Java to Program Files, ANT will complain about this later (since Ant sits on top of Java).
   * Add **C:\whatever\android-sdk\platform-tools** to your windows path
   * Add **C:\whatever\android-sdk\tools** to your windows path
@@ Line 66: / Line 69: @@
   * In Settings->Applications->Development enable "USB debugging"
   * After plugging in your phone, in the Win device manager it will probably say "no drivers installed" - click update driver and install them
-  * Typing "abd devices" should show your plugged in phone as a device now.  If so, congrats, you got this far!
+  * Typing "adb devices" should show your plugged in phone as a device now.  If so, congrats, you got this far!