Closed IriaSomobu closed 4 years ago
I am fine with this, as I do not have any android studio/gardle experience.
I may readd a makefile based build that works with the new structure besides the up to date gardle setup, because this allows building the project with vanilla debian packages.
Sure you can, but:
library
subproject as Maven artifact on bintray (it'll very useful to anyone who wants to embed library in own project), this can be done rather easy using com.novoda.bintray-release
gradle plugin but I have no clue how to do it using makefile without pain and suffering.Of course gradle has some flaws: if you dont have system-wide gradle
and using ./gradlew
from project folder, it'll load at first launch about 150mb of own build tools, but I think this is reasonable price for such convenience.
Ok, then I'll try to educate myself and start using gradle. Is there a way to add a assets folder using this build system (Without the need to install Android Studio)? I use this project to launch some of my C++ FLTK programs and for this I usually copy the binaries to the assets folder. (Maybe you know a better trick?)
Another approach to run binaries on Android is to compie them into shared library and communicate with them via JNI. But I'm not sure that it is better trick because JNI is complicated on C side.
As for assets/
folder within .apk
file, you can simply create assets/
folder near the res/
. All files from here will be copied into corresponding folder in .apk
.
Ok thanks, I already messed around with the jni stuff, but for my current project i really just want to execute a normal elf executable. (I basically wrap this XServer around my binary and start it using the java processbuilder).
This PR changes structure of project to follow modern Android development practices:
library
(containsXServer
and all related resources) anddemo
(fromXDemo
);So with this PR applied you can just open this project with Android Studio and everything will work out-of-the-box.