JOGL OSX and eclipse

OpenGL Development JOGL Development
#1

I’m having two problems since I moved my development environment to OSX (Tiger), help on either would be appreciated.

  1. when running fullscreen mode, any dialog popup just makes the whole screen go black.

  2. I can’t start my application from within eclipse (runs fine if I build local webstart version) I get the following error:
    Exception in thread “AWT-EventQueue-0” java.lang.UnsatisfiedLinkError: createPixelFormat1

my java.library.path is pointing to the following files:
…/lib/mac/libgluegen-rt.jnilib
…/lib/mac/libjogl_awt.jnilib
…/lib/mac/libjogl.jnilib
…/lib/mac/libjogl_cg.jnilib

Also tried the latest version of 231, although I suspect these are mac Java issues. Please Sun, take over the OSX JVM and bring us Java6 :slight_smile:

Peter

#2

If you are going to be running your development projects from within Eclipse, then what you need to do is to put the native libraries in the base of your project and then add the jars to the project. The other alternative location is ~/Library/Java/Extensions. Both will do the job.

#3

The set-up I had worked fine under windows with the native libs in sub folders. But I tried the suggestion of putting them into the root of the project, but same error as above.

I really don’t want to put them into the Extensions folder because I have two project running different versions currently. But so far that’s the only solution I’ve seen via google and here.

If I make the java.library.path invalid, then I get a different, and expected error of:
Caused by: java.lang.UnsatisfiedLinkError: no jogl in java.library.path

So it seems to be finding jogl, or at least some of it…

Peter

#4

Please don’t suggest this. It possibly breaks installation of JOGL Webstart applications.

I just want to confirm, that your library.path setup does not seem to be the problem here. Maybe your natives are for a different jogl version or for the wrong architecture… are you using the universal builds?

#5

Thanks! It was something as silly as the version between the jars and natives I think. Eclipse was pulling the jar still from my windows subdir rather than my mac subdir. I should have spotted that but I convinced myself it was the natives.

Cheers
Peter