executable jar, jogl, native interfaces

OpenGL Development JOGL Development
#1

I want to package my jogl application into an executable jar for distribution along with the native interfaces. When I do this however, I get a complaint about missing the native interfaces.

I dont want to require the end users to download the native interfaces and install them. I would like the jar to be entirely self-contained.

I have so far been unsuccessful at find a solution. I couldn’t find anything on this forum and google wasn’t much help. What do you use when you want to package your jogl apps for distribution?

#2

For windows I use an installer to install the application into a target-directory containing my application and the native libraries. To start the application I use either a bat file or a corresponding link to javaw.exe with the execution directory set to the folder where the native libraries reside.

#3

Take a look at the new Import Facility in Java Web Start in J2SE 5.0. This allows you to do a CD install of an application described by a JNLP file, so you can use one uniform file format to describe your application both for running locally and over the web. Combined with Java Web Start’s desktop integration features I think this is a pretty powerful and portable way of making a Java app look like a native desktop app.

#4

[quote]Combined with Java Web Start’s desktop integration features I think this is a pretty powerful and portable way of making a Java app look like a native desktop app.
[/quote]
…Except that it, sadly, requires a pre-installed JRE on the end-user’s computer. Also, I really hate the amateurish look of the Web Start splash screen and the warnings it spawns, when the user is about to do something really “dangerous” (as in run the program).

#5

Thanks for the info. Looks like I need to take a look at web start. This was my first post and response on this forum was great. Ill be posting pretty regularly and trying to help people where I can.