SFML community forums
Bindings - other languages => Java => Topic started by: pdinklag on December 18, 2014, 06:53:11 am
-
This is just a little sign of life. ;)
Life is keeping me very busy these days, I hope that I can find some time to update JSFML for the new SFML release sooner than later.
From what I've seen, there are not many API changes, so it should all go relatively quick once I find some time.
The problem will be - as always in the past - building and packaging the native (C++) part. I don't have any Linux development systems I use regularly, so the ones I used last are heavily outdated. I also don't own a Mac to build the OS X version. If anybody could help out here, I'd highly appreciate it.
-
For the Mac version, ping me when it's ready to be built. ;)
-
Does your computer have 6 gigs of RAM or more? If it does a virtual machine might help with getting a Linux Development system running.
-
I applied the SFML 2.2 updates, although they are untested for now.
For the Mac version, ping me when it's ready to be built. ;)
Thanks! :) I will get to you about this once I tested the updates, so you won't have to build unstable builds.
Does your computer have 6 gigs of RAM or more? If it does a virtual machine might help with getting a Linux Development system running.
Yep, that's what I did before. I had two virtual boxes, one for Linux x86, one for Linux x64. At some point this year, I got rid of them, but I might go for that setup again.
-
I run Linux 64-bit, so I might be able to help with that part of it ^.^
-
Well, what I need are the shared object files (except for networking) of SFML 2.2 built for Linux x64 with libglew-1.5 (or is it 1.6?) and libjpeg8d linked statically. It's messy, I know, but I failed to find a better way to solve those dependencies (e.g. Fedora does not have libjpeg and many systems only have libglew-1.7 or later).
Then the native part of JSFML needs to be built on Linux x64 as well (using "ant linux64") - the output file libjsfml.so needs to be packaged in the release jar.
I'll have to set up some VMs again to make it an automated workflow, but I don't look forward to the effort, especially since VirtualBox had a lot of problems with Debian 7 and/or my host system.
-
I have the shared object files, but my version of GLEW is 1.12 so I'll compile the older version from source if needed. As for libjpeg8d, I only have libjpeg (I don't know if they're the same thing)
I don't know how to use ant, but I have the JSFML shared object files in the home directory
If that's everything that's needed, then I'll be glad to try compiling it at once :3
-
You should be able to verify your libjpeg version by asking your package repository. I don't think 8d is required, I always used the latest. The key is that it needs to be linked statically for distributions like Fedora, which only comes with libjpeg-turbo.
About libglew, that's what I did. Grab an old version (should be 1.5) and compile it myself - it also needs static linking. For what I remember, SFML's cmake script will complain about newer libglew versions, unless that was changed or there were other reasons. It's been a while. :-[