
Signature
Dr Jon D Harrop, Flying Frog Consultancy
http://www.ffconsultancy.com/products/?u
> >> Anyone managed to get JOGL working under AMD64 Debian?
> > Only with Nvidia video cards and their *sinful* binary drivers. ATI is a
[quoted text clipped - 19 lines]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
This seems to be a classic classpath problem. Probably the basic jogl jars
are not in the system class path, so you would have to specify them
explicitly. Also make sure that the native libs are in the library
path. Otherwise, this is going to be your next problem.
> So I tried getting a coherent distribution from the latest stable releases
> (jogl-1.1.1-rc3) but I still get the same error. I've tried recompiling the
> whole thing from scratch and still get the same error.
The thing is that you specify "java -cp build/jogl-demos.jar", and I assume
that the proper jogl jars aren't in the demos and they're not in the system
jar folder.
> Finally, I've scoured the internet to see if anyone else has working
> implementations. I found a couple of demos that run under web start. One of
> my browsers under (64-bit Debian) Linux handles this and the demo runs but
> it is very slow. However, it is layering both Java2D and OpenGL so maybe it
> is inherently slow. The same demo on my Windows XP box (same hardware) runs
> for a few seconds before hanging.
Can't tell you what is wrong. I have JOGL running under Linux and WinXP
without that much hassle. I just followed the instructions. The problems you
have described so far are nothing specific to your 2 processor architecture or
64-bit system.
> 1. If I want to do high-performance real-time interactive 2D and 3D graphics
> and port our OpenGL-based libraries to the Java platform for others to use,
> is JOGL the right library for me?
Haven't checked LWJGL, but the two are the only ones to consider as far as I
can see. You could write some benchmark and compare the two. There were
claims that JOGL is within a single digit performance from C. (I currently
only find a claim to within 15%.)
> 2. How many people actually have a working JOGL development environment, so
> they can compile OpenGL applications written in Java?
I do. I compile on Linux and test also on WinXP, since native code is
involved. Didn't have any problems.
> 3. How reliable is JOGL? Is it viable to use JOGL for commercial work or is
> it too unstable in practice?
I can't tell. The featured projects and the list of references to code
suppliers seem to suggest so. I didn't have any stability problems. (I do
have some weird mouse pointer "loss-of-resolution" problems when opening an
OpenGL window in X11. I haven't come around to checking why this is so.)
Michael
Jon Harrop - 11 Oct 2007 06:55 GMT
>> >> Anyone managed to get JOGL working under AMD64 Debian?
>> > Only with Nvidia video cards and their *sinful* binary drivers. ATI is
[quoted text clipped - 24 lines]
> explicitly. Also make sure that the native libs are in the library
> path. Otherwise, this is going to be your next problem.
Yes indeed! I posted on c.l.java.help and they explained that you cannot
pass jars using several -cp arguments, you must use a different syntax for
passing the classpath on command line:
java -cp ../jogl/build/jogl.jar:../gluegen/build/gluegen-rt.jar:build/jogl-demos.jar
demos.gears.Gears
As you say, I have to setup my LD_LIBRARY_PATH first to find the native code
DLLs:
export
LD_LIBRARY_PATH="/home/jdh30/src/jogl/build/obj/:/home/jdh30/src/gluegen/build/obj/"
and then the whole thing works!
Thanks to everyone for their help.
>> So I tried getting a coherent distribution from the latest stable
>> releases (jogl-1.1.1-rc3) but I still get the same error. I've tried
[quoted text clipped - 3 lines]
> assume that the proper jogl jars aren't in the demos and they're not in
> the system jar folder.
Yes, there are other requires jars in ../jogl/build and ../gluegen/build but
even if you reference them like this:
java -cp ../jogl/build/jogl.jar -cp ../gluegen/build/gluegen-rt.jar -cp
build/jogl-demos.jar demos.gears.Gears
it still doesn't work.
Perhaps the best solution is to set the CLASSPATH environment variable and
give absolute paths to the jar files:
export
CLASSPATH=/home/jdh30/src/jogl/build/jogl.jar:/home/jdh30/src/gluegen/build/gluegen-rt.jar:/home/jdh30/src/jogl-demos/build/jogl-demos.jar
Note that you must give absolute paths to the jar files themselves and not
just the directory they reside in (which is one of the things I was doing
wrong before).
>> 1. If I want to do high-performance real-time interactive 2D and 3D
>> graphics and port our OpenGL-based libraries to the Java platform for
[quoted text clipped - 5 lines]
> claims that JOGL is within a single digit performance from C. (I currently
> only find a claim to within 15%.)
Great, thank you. I'm really only interested in reliability at this point
and it looks like JOGL is the defacto standard, so I'll stick with it.
>> 3. How reliable is JOGL? Is it viable to use JOGL for commercial work or
>> is it too unstable in practice?
[quoted text clipped - 4 lines]
> opening an
> OpenGL window in X11. I haven't come around to checking why this is so.)
Ok. I'll give it a go and see what I come up with. I'll also blog exactly
what I had to do to get it working.
Many thanks for all your help.

Signature
Dr Jon D Harrop, Flying Frog Consultancy
http://www.ffconsultancy.com/products/?u
Michael Jung - 13 Oct 2007 16:43 GMT
> java -cp ../jogl/build/jogl.jar -cp ../gluegen/build/gluegen-rt.jar -cp
> build/jogl-demos.jar demos.gears.Gears
Use colon separators instead of multiple classpath options.
> Perhaps the best solution is to set the CLASSPATH environment variable and
> give absolute paths to the jar files:
> export
> CLASSPATH=/home/jdh30/src/jogl/build/jogl.jar:/home/jdh30/src/gluegen/build/gluegen-rt.jar:/home/jdh30/src/jogl-demos/build/jogl-demos.jar
Your choice. In some situation this obscures things.
Michael