I’m having a problem launching a JOGL applet in linux. The error we’re getting is the infamous “UnsatisfiedLinkError: no gluegen-rt in java.library.path.” We aren’t using the JNLPAppletLauncher, and have replaced that same type of functionality with our own.
The problem is that even though we have (supposedly) loaded gluegen-rt ourselves, the com.sun.opengl.impl.x11.DRIHack.begin() method is eventually attempting to load it itself using System.load(“gluegen-rt”), because gluegen’s NativeLibLoader.loadLibraryInternal(“gluegen-rt”) knows that the JNLP applet launcher wasn’t used.
Another peculiarity is that NativeLibLoader.disableLoading() has been called in our own code before launching the applet, but loadLibraryInternal() is still being called from loadGlueGenRT(), which seems to be checking that. Maybe someone is resetting it?
We also have our own class loader which we can set in the thread but this has no effect, I believe, because a new thread is spawned
Does anyone know how I can reliably disable loading of gluegen-rt? I’m sure I could figure this out by building JOGL and debugging it myself but I don’t have the time at the moment.
Thanks,
Dale