| Summary: | Make it possible to specify the name of native libraries | ||
|---|---|---|---|
| Product: | [JogAmp] Jogl | Reporter: | Sven Gothel <sgothel> |
| Component: | core | Assignee: | Sven Gothel <sgothel> |
| Status: | VERIFIED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1 | ||
| Hardware: | All | ||
| OS: | all | ||
| Type: | FEATURE | SCM Refs: | |
| Workaround: | --- | ||
you can specify a lib path |
---- Reported by fabriziogiudici 2007-11-17 08:29:31 ---- There are some problems if people try to integrate JOGL with NetBeans RCP and want to run on more than one Unix (e.g. Linux + Solaris) or Windows (e.g. 32 + 64bits) system. This is due to the fact that NetBeans expects that all the native libraries for a given component are packed in the same directory - hence the problem since all Unix systems share the name libjogl.so. It's clearly not a JOGL problem but a NetBeans problem, but it won't be solved in a short time. Evaluating a few workarounds to this, it seems to me that the thing that would make the programmer's life easier would be a set of properties (e.g. jogl.nativelibrary.name.{jogl,jogl_awt,jogl_cg} or whatever) that could be used to override the default names of the searched libraries. Not specifing them would have the system behave as today; their presence would allow the programmer to rename the native libraries (e.g. libjogl-linux-64.so), guess which the current operating system is and compose the proper library name. Leaving the o.s. detection and consequential the choice of the library name to the programmer should make this RFE a low risk for JOGL developers. --- Bug imported by sgothel@jausoft.com 2010-03-24 07:51 EDT --- This bug was previously known as _bug_ 333 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=333