This isn’t really related but I asked the JSR 198 expert group about loading native libraries and managing native dependencies with JSR 198, the Java IDE standard because I someday may want to use JOGL in a plugin. Here is the response I got:
[quote]As I said in my previous reply to your question
the JSR does not provide a standard way to
to define dependencies to native libraries.
What the JSR provides is an API clients can call to
get their extension path: ExtensionRegistry.getInstallRoot().
This API can be used to get at the directory where
your native library resides as follows:
import javax.ide.extension.ExtensionRegistry;
import javax.ide.net.URIFactory;
import javax.ide.net.VirtualFileSystem;
…
final Extension myExt =
ExtensionRegistry.getExtension("my.extension");
final URI extPath = ExtensionRegistry.getInstallRoot(myExt);
final URI libPath = URIFactory.newURI(extPath, "lib");
final String path =
URIVirtualFileSystem.getPlatformPathName(libPath);
Now you can use the System.loadLibrary( path )
method call to load your native library.
You also must take care to package
your extension into a JSR 198 extension bundle archive
(EBA), and to place your files as specified by the EBA
specification:
- my.extension.jar => extension jar
- my.extension => extension directory must have
same name as extension
jar.
- my.extension\lib\my.dll => native library
The EBA is installed in an IDE’s extensions directory.
I hope this answers your question.
Jose.
[/quote]
I am not too familar with the latest open IDE API but if it support file paths for modules then the above approach my work for managing JOGL version dependencies
