Posted by Alexis Drogoul on Jun 01, 2015; 8:19am
URL: https://forum.jogamp.org/Return-of-the-java-lang-UnsatisfiedLinkError-Can-t-load-library-System-Library-Frameworks-gluegen-rt-tp4034549p4034556.html

Hi,

Thanks for your answers and pointers.

No problem to run the tests under MacOS X 10.10.2 and JDK 1.8 (this is one of the configurations that failed on Eclipse Luna) — jogl is up and running and the jars are picked in the right directory (the "jar" directory within the jogamp-all-platforms folder).

All the directories listed for the soon-to-be-abandoned extensions mechanism by the JDK

(namely : /Users/YOUR_NAME/Library/Java/Extensions
/Library/Java/JavaVirtualMachines/YOUR_JDK/Contents/Home/jre/lib/ext
/Library/Java/Extensions
/Network/Library/Java/Extensions
/System/Library/Java/Extensions
/usr/lib/java)

have also been cleansed from anything related to j3D, gluegen and jogl (easy: there was nothing as I had already emptied these extensions before).

Now, under the same configuration, things happen randomly : sometimes it works, sometimes it doesn't. The same with a colleague of mine who runs under 10.9.5. Could the "Resolver" we set the first time a JOGL view is opened be rewritten somewhere with a default value ? (I dont think so as this possibility is tested in JarUtil, but who knows ? Reflection can make miracles :)).

I'm a bit lost, actually. Will continue digging, of course, but I dont know exactly in which direction !

Alexis