02-29-2016, 06:56 AM
(This post was last modified: 02-29-2016, 07:45 AM by Schwertspize.)
A bit bad..... Because IMHO we don't want to use jni (and for Android the NDK) for that, because that would tight cuberite too much to the app. In particular that means we have to build a new apk file with every new version, especially when using the app store that is bad because then people don't get updates when they want to use it (app store has delay), they get updates every day they DONT want to use it. Way better and a much cleaner approach would be implementing kind of a wrapper which downloads binary and libraries from the build bot.
Edit: @sphinxc0re you are wrong. After writing a few emails with him (I got instant replies) he made clear that he wasn't playing with jni, he was actually dropping everything he doesn't need. In reality, I wanna provide a quote from an email:
He then said if he would finish it, it would be nice if he had a branch or whatever containing his cluster-oriented cuberite flavor.
Edit: @sphinxc0re you are wrong. After writing a few emails with him (I got instant replies) he made clear that he wasn't playing with jni, he was actually dropping everything he doesn't need. In reality, I wanna provide a quote from an email:
Quote:I have a 5-Raspberry Pi cluster sitting around and I thought it'd be cool to put a Minecraft server on it capable of using all 20 cores and 5gb of RAM. I forked Cuberite and plan to strip it down and MPI-ify it.
He then said if he would finish it, it would be nice if he had a branch or whatever containing his cluster-oriented cuberite flavor.