The jogamp 32bit libs only work with 32bit os opengl drivers. Your os probably only contains 64bit opengl libraries so it will not work. The problem is that compilers do not allow compilation of a 32bit jni lib that can link to 64bit system libs.
2013-01-22 16:16 skrev MDHillman [via jogamp]:
I currently have a Java application that, at run time, attempts to set Java's library path to the 64Bit Gluegen & Jogl DLLs then tests them, if this test fails, the 32Bit libraries are loaded.
This seems to work unless I'm using a 32Bit JVM on a 64Bit OS, where neither libraries work. I've tried using the native JAR files but these don't seem to work either.
Any ideas how to address this?
If you reply to this email, your message will be added to the discussion below:
I've added the JOGL and Gluegen jar files from the central maven repository (POM below). It was my understanding that the loading of native libraries was all handled by JOGL/Gluegen and that once I'd added these dependancies I wouldn't have to do anything. Saying that, I still get "no gluegen-rt.dll in library path" errors. Have I missed something?
The JARs containing the native libraries must be in the same directory than the JARs containing Java libraries. Maybe the extraction and loading of native libraries does not work in your case. Do you modify the Java library path? Ardor3D uses Maven with JOGL 2.0 and it works very well. As Xerxes said, you need a 32 bits OpenGL driver to use 32 bits native libraries for JOGL.
Well, actually, the sole reason that gluegen-rt-main and jogl-all-main exist are to create a dependency on the other artifacts that provide the native libraries. Maven must (as a fundamental part of how it deals with artifacts) pull in all of those dependencies into the local package cache if they don't already exist.
You can see the jogl-all package here, with all of the associated native library jars: