TGUI 0.7 is no longer supported, use a newer TGUI version instead.
Due to regular breaking changes in SFML, android will only remain supported in TGUI 0.8.
Please note that support for android is still in an early stage. Building for android has so far only been tested on linux, altough it should be very similar on other systems.
Using TGUI was only successfully tested with android-ndk 12b and with ANDROID_STL=c++_shared set in cmake (which is the default value).
You must have already build SFML for android and verified that you can run your sfml app on your device or emulator. Only then should you proceed with installing TGUI. This also means that the Android SDK and the Android NDK are thus already setup correctly. Especially make sure that the ANDROID_NDK variable is set so that the installed SFML files in it can be found automatically.
You will need to use CMake in order to build TGUI. You can download the latest version here.
If you create the .apk file through the command line like described below then you will also need Apache Ant.
From inside the TGUI folder that you download execute the following. The ANDROID_ABI should be set to the ABI that you want to use, this will most likely be "armeabi-v7a", but you can also set it to "armeabi", "x86" or "mips". On windows you might also have to pass your generator to the cmake command with the -G parameter. On linux and mac "Unix Makefiles" will be used by default.
Make sure that it finds the android sfml libraries. If you see a message like "Found SFML 2.4.2 in /usr/local/include" then it is finding the ones for your own system instead. Remove the libraries from /usr/local/lib and the includes from /usr/local/include, delete the cmake cache and rebuild. After that it should find the ones in the android ndk.
Depending on the generator, CMake will have created a build file or project. For "Unix Makefiles" (default on linux and mac) you use the following code to build the library and install it to the ndk folder. The "-j2" after the make command means it uses 2 threads, if you have more cores you can increase the number to speed up the build.If you get tons of linking errors after running make then double check that you are including and linking to the android sfml libraries and not the ones for the OS that you are running.
To test if everything is working, you can build the example code.
If you have build TGUI with a different ABI (e.g. you used x86 instead of armeabi-v7a to run it in a simulator), then make sure to edit APP_ABI in jni/Application.mk inside the android example folder, otherwise you can get the error that TGUI.hpp is not found.
First you have to run ndk-build. You can do this by opening your console inside the TGUI/example/android folder and running the following.
If this succeeds then you can build the apk. The target sets the API level to use (you need this version of the android SDK installed).
You can now install the .apk file to your android device (or a running simulator) with adb. Note that the adb server might have to run as root to have permissions to access the android device.
If you don't have much experience with android then your can just use the tgui demo code as a starting point. But below I will explain some settings that you need in order to use tgui if you have your own project set up.
In the Android.mk file you must add the tgui library
You also have to import tgui in that file. Importing sfml is not needed as tgui will already do that for you.
In Application.mk you must enable exceptions and RTTI and add the tgui-activity module
Finally you have to load the tgui-activity so that it can load the tgui library. You do that by having this in your AndroidManifest.xml file
That's it. You should now know enough to use tgui in your project.