Posted by gouessej on Jun 08, 2016; 9:47pm
URL: https://forum.jogamp.org/J3D-JOGL-good-within-Eclipse-but-UnsatisfiedLinkError-as-standalone-tp4036783p4036812.html

Hi Larry

Larry Tesler wrote

Julien,

gouessej wrote

It's explained in the Java3D user's guide I wrote...

At what URL is the most current version of your guide?

EDIT: If it's https://gouessej.wordpress.com/2012/08/01/java-3d-est-de-retour-java-3d-is-back/, I have read it many times. It is dated 2012 but it does seem to link to the late 2015 archive. I'll try to follow it again.

My tutorial is frequently updated, there is no need to rewrite it from scratch. I update it only when I'm sure of what I'm going to do in order to confuse my readers.

Larry Tesler wrote

gouessej wrote

P.S: Actually, if you really want to build Java3D, you should use my repository but ... it's Java3D 1.7.0, the imports aren't the same...

Is https://libraries.io/github/scijava/java3d-core the repo you speak of? If not, what is the URL of the repo you meant and what are the major pros and cons?

EDIT: I see that scijava is ctrueden's and yours are at https://github.com/gouessej?tab=repositories.

gouessej wrote

Relying on the extension mechanism is a really poor decision

I won't.

Thanks,

Larry

ctrueden's fork isn't maintained by the JogAmp community. ctrueden's contributions have been very valuable :)

I was talking about my repositories:
https://github.com/gouessej/java3d-core
https://github.com/gouessej/vecmath
https://github.com/gouessej/java3d-utils

Larry Tesler wrote

Please keep in mind that my current tool set is Eclipse (4.2.2), CVS (not yet git or svn) and ANT (not yet Maven). Once I have released the next version of BigOldApp, changing to a different tool set for subsequent releases will be very much on the table.

If I could get past these Java3D issues, BigOldApp would be essentially ready to release. I am oh so close...

Larry

Actually, when I look at your very first error message, I assume that you packaged your software with the wrong version of the JRE, there is a problem of bitness. You try to use a 64-bit JRE with 32-bit native libraries.

I've just looked at your very first stack trace and I can confirm that your program doesn't use Java3D 1.6 or 1.7, there is no call to System.loadLibrary() in the MasterControl class since the pre-build in which I removed the native renderers:
https://github.com/gouessej/java3d-core/blob/master/src/main/java/org/jogamp/java3d/MasterControl.java