---- Reported by soulfly32 2005-08-02 10:02:46 ---- Its a way diffycult to offer JOGL-programs to other people. Copy jar to this folder and the dll/so files to this folder. An integrated LibLoader would be very nice. Then you only need to specify (out of your programm) the folder where those libs are. ---- Additional Comments From jaeden 2005-08-02 10:33:13 ---- Also see issue 172 for a sample fix for this ---- Additional Comments From kbr 2006-01-11 00:56:43 ---- JOGL currently offers two deployment strategies neither of which involves any manual installation of files on the end user's machine. First, JOGL is available as a Java Web Start extension, which is how all of the jogl-demos are deployed. Second, with the new JOGLAppletLauncher it is possible to deploy unsigned Java applets which use JOGL with no manual installation of any files. I believe these two deployment mechanisms, in conjunction with new support in Java Web Start in JDK 5 like the Import Facility (see http://java.sun.com/j2se/1.5.0/docs/guide/javaws/enhancements-1.5.0.html), should be sufficient to cover most deployments of Java Web Start applications. I do not think it is a good idea to standardize some directory structure in the JOGL internals where if a certain API is called with the root of the directory structure then the code searches through it for the appropriate native library to load. This is exactly what Java Web Start is designed to abstract away. I apologize but I'm closing this bug as "will not fix". Please investigate Java Web Start more thoroughly; I think you will find it surprisingly flexible for distributing applications. --- Bug imported by sgothel@jausoft.com 2010-03-24 07:47 EDT --- This bug was previously known as _bug_ 171 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=171