Eclipse and Exporting JoGL

Sorry for another dumb question, but I'm having a lot of trouble getting Eclipse to export executable jars...  I have everything linked in a custom library, but when I export to a jar, it's not working... my guess is that it's because the native libraries aren't getting exported.  Is there an easy way to do this?

Hi!

Rather use Ant to make a JAR in Eclipse and use the JARs of JOGL 2 that contain the native libraries to deploy your application. If it is not clear, look at my build.xml files.

I'm sorry, I don't follow you there...  Could you explain a bit more?

I remember with the old version of JoGL you could just make a fat jar with the jogl jars... that doesn't seem to be working anymore.  My goal is to just have a jar i can give someone that they can run.

Thanks,
Nick

It has nothing to do with JOGL. Since Java 1.6 update 21, the JARs are handled a bit differently, it is hardly possible to mix signed and unsigned JARs.

What you intend to do is impossible because JOGL uses native libraries, not only JARs. Rather use Java Web Start if you want to create a very simple installer. The user has just to click on "OK", it is not difficult :)

I use Ant to deploy my project, everything is automatized. The Ant script (build.xml) compiles the source code, make several JARs, sign them, generate the JNLP files. At the end, I only have to copy the content of the "target" directory onto my FTP server on Sourceforge.net and my friends only have to click onto a JNLP link to launch the installation.

On Friday, October 15, 2010 01:10:45 gouessej [via jogamp] wrote: this is our solution, jogl commit 14256647c8954bb8d6d2afa88927e75783bc912b
http://github.com/sgothel/jogl/commit/14256647c8954bb8d6d2afa88927e75783bc912b

~Sven

Hi!

Sven Gothel wrote

this is our solution, jogl commit 14256647c8954bb8d6d2afa88927e75783bc912b
http://github.com/sgothel/jogl/commit/14256647c8954bb8d6d2afa88927e75783bc912b

It is a nice solution especially for the applications that do not need to be signed. In my case, it is better to use the same signature for all JARs.

Here's a tutorial that explains how we do it at work: http://wadeawalker.wordpress.com/2010/10/24/tutorial-creating-native-binary-executables-for-multi-platform-java-apps-with-opengl-and-eclipse-rcp/

This way is done from inside Eclipse instead of through a build script, so it's not as automatable as the two other ways that have been mentioned here. But it might be easier for someone who works inside Eclipse and doesn't do a command-line build process.