I happen to be on x64 Linux much of the time these days with a 64-bit JVM. I got around to looking at the latest Fan build recently, and the FWT code didn't run because of missing 64-bit so files for SWT or whatnot. Just figured I'd report the issue.
brianWed 29 Oct 2008
Yeah right now I just include 32-bit GTK, Win32, and Mac OS X. Those 3 as is take up a ton of space. All you need to do is download the correct SWT for your platform from here. Then replace the files in your "lib/java/ext/linux" directory.
Right now I'm building the path in the bash script in "bin/fanlaunch" - I guess really we should take 32-bit versus 64-bit into account in that script and use different extension paths. Although I'm not sure exactly how to figure out from bash whether you are on 32-bit or 64-bit.
Also note the Windows launcher doesn't support 64-bit, but it is on our todo list.
tompalmerFri 31 Oct 2008
I replaced the SWT, and things worked on. Might not be best, but uname -a does give the CPU type among other things. And java -version indicates 64-bit, too.
brianFri 31 Oct 2008
Ok, I'm not too familiar with uname, but we definitely need know it before we start the VM so that we can set the executable path to find the native libraries.
This is actually a really complicated issue. There are two paths Fan can take:
one distribution with common platforms all bundled in
different Fan distributions for multiple platforms
Both solutions have different trade-offs. The problem in both cases is that slicing platforms tends to be a multi-dimensional problem. For example we might slice SWT by OS, microprocessor, or graphics technology.
I'd like to hear suggestions on how others wish to tackle the platform/distro strategy - especially with regard to SWT. What are the key platforms? Right now I've doing:
tompalmer Wed 29 Oct 2008
I happen to be on x64 Linux much of the time these days with a 64-bit JVM. I got around to looking at the latest Fan build recently, and the FWT code didn't run because of missing 64-bit so files for SWT or whatnot. Just figured I'd report the issue.
brian Wed 29 Oct 2008
Yeah right now I just include 32-bit GTK, Win32, and Mac OS X. Those 3 as is take up a ton of space. All you need to do is download the correct SWT for your platform from here. Then replace the files in your "lib/java/ext/linux" directory.
Right now I'm building the path in the bash script in "bin/fanlaunch" - I guess really we should take 32-bit versus 64-bit into account in that script and use different extension paths. Although I'm not sure exactly how to figure out from bash whether you are on 32-bit or 64-bit.
Also note the Windows launcher doesn't support 64-bit, but it is on our todo list.
tompalmer Fri 31 Oct 2008
I replaced the SWT, and things worked on. Might not be best, but
uname -adoes give the CPU type among other things. Andjava -versionindicates 64-bit, too.brian Fri 31 Oct 2008
Ok, I'm not too familiar with
uname, but we definitely need know it before we start the VM so that we can set the executable path to find the native libraries.This is actually a really complicated issue. There are two paths Fan can take:
Both solutions have different trade-offs. The problem in both cases is that slicing platforms tends to be a multi-dimensional problem. For example we might slice SWT by OS, microprocessor, or graphics technology.
I'd like to hear suggestions on how others wish to tackle the platform/distro strategy - especially with regard to SWT. What are the key platforms? Right now I've doing:
But 64-bit is going to becoming more common.