lynx Posted October 7, 2015 Share Posted October 7, 2015 No, I'm not touching the driver itself, just trying to add it to the android build system. Link to comment
spk Posted October 11, 2015 Share Posted October 11, 2015 Hey, I've been following this thread (have an N7, same version, etc) trying to get GemRB to load as well. Just thought I'd post some info I've figured out while trying it out. * The OpenAL failure appears to be due to the library openal not being initialised at startup (the GemRB code calls openal, which in turn tries to access a JNI which hasnt been initialised) * SDL does a similar thing, but in this case, it DOES get initialised and that's why that bit doesn't crash. * Google consensus suggests GemRB loads the SDL library on startup (searched for how to initiliase libraries at startup) * This is done in GemRB.java which references the SDL library * Attempt at doing the same thing for openal by me has been met with failure (cant extend a class by multiple classes) Other stuff: * Peyla's build doesn't include gemrb any more * found references in git log for gemrb about removing all reference of peyla, (maybe the build script has that reference as a leftover artifcact) Going to go carry on poking around - pretty sure theres a way around this. Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 Yeah, pelya used a custom sdl port, which we used initially (before sdl2 was even named). I suggested perhaps trying his packaging of openal. Doesn't get initialised? We use a loadLibrary call for it like with SDL2. Unless it doesn't go by "openal" for some reasons or more than that is needed. Thanks for investigating! Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 Haha, that's it!prep_env injects the library lines, but upstream sdl changed, so the pattern didn't match anymore. Fixing ... done.new test build available here (but you can roll your own):https://sourceforge.net/projects/gemrb/files/Other%20Binaries/android/0.8.3/ Link to comment
spk Posted October 11, 2015 Share Posted October 11, 2015 Aha! Yes, I managed to chain classes together in the java build and got it working. So was fiddling with the prep_env to build the extra folders, and noticed the exact library injection lines you just pointed out! Will clone fresh and build to see what happens... Link to comment
spk Posted October 11, 2015 Share Posted October 11, 2015 failed to build: looks like line 213 in prep_env contains an extra android-project that isnt needed Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 that bit was weird, yes, I changed in the last commit. I've reverted it now: on a fresh build dir it is clear just something got broken in my previous setup. Link to comment
tormentor Posted October 11, 2015 Author Share Posted October 11, 2015 @spk: Thank you for helping to spot that. Sometimes an extra pair of eyes is all that's needed. Looks like GemRB on Android is a thing again, then with sound! Link to comment
Mad Mate Posted October 11, 2015 Share Posted October 11, 2015 Great work, guys! Thanks for all your work. I would be nice to post latest android builds somewhere, for the rest of us, who doesn't know how to build them. Also, Windows buildbot stopped working on 24.09. Thanks again! Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 Mad Mate: what's wrong with the link above? Link to comment
Mad Mate Posted October 11, 2015 Share Posted October 11, 2015 Yes, it works, but I meant more regular builds like the ones with build-bot. You make a lot important changes with each commit, so new builds are always welcome. Link to comment
tormentor Posted October 11, 2015 Author Share Posted October 11, 2015 Self compiled version fails to run now. See attachment meh, attachment failed. Where's the net.sourceforge.gemrb-1 coming from? In my case, it's net.sourceforge.gemrb where the app is installed. Also there is a libpython tarball in the gemrb git checkout, but apparently some paths were changed in the install script or something. Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 We don't have a build slave for android, so there are only builds when someone makes them. Thanks for reminding me about the bot; it's disk is full. Link to comment
tormentor Posted October 11, 2015 Author Share Posted October 11, 2015 Building for android isn't hard now; you just need to follow the readme. This means installing the android SDK and NDK, running the prep_env script, running ndk-build && ant debug. You'll need a Linux system, but Ubuntu is free Otherwise, poke someone on the forum if you want a fresh build. Link to comment
lynx Posted October 11, 2015 Share Posted October 11, 2015 ah, that should be trivial - the filename is actually libpython2.6.so. Gimme 5. edit: done and refreshed the build on sourceforge. Oh, this time an "-unsigned" version if it makes any difference. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.