After each successful step I've copied whole test project folder to another one, and continued refactoring further. I've downloaded and installed Android studio, created simple JNI (Java + C++) sample project and started iterating it through. Using newer gradle - up to godot level or up to Android studio level sounded like mission impossible.įinally I've decided to restart everything, and went down to basics and beginning. Visual studio was also based on old gradle. Android studio does, but my needs were relatively simple, no need for fancy gradle scripting. I've liked what godot adle looks like - one configuration file and nothing fancy.īesides this Visual studio itself does not provide code syntax highlightning or intellisense for gradle. Visual studio and Android studio both provide a wizard, which can generate some sample project, but sample project is rather messy in overall - a lot of unnecessary configuration files. And that turned out to be bit complex project itself. Visual studio itself provides an examples of gradle demo project, but they do contain only java - I wanted to have in similar manner to godot both - C++ and Java. Gradle build system is believably complex. I've used visual studio for compiling godot on Android, as well as building gradle packaging. StoreFile file('./././debug.keystore')įinally I've managed to compile somehow working version of godot. you could add them into your module gradle to try it out.

the following are default when you choose debug build inside android studio ProguardFiles.add(file('proguard-android.txt')) Both signing and zip-aligning will be done at export time I have tried to use following configuration in adle - but gdbserver is still not added to. apk (at path /lib/armeabi-v7a/gdbserver) - then native debugging starts to work. At least what I have tried out in Visual studio, gdbserver must be in. I want to try out how to debug godot engine on Android, and in order to do that one - I suspect I need to add gdbserver into.

Android studio logcat messy