| Deploying dependent .dlls with branded platform (best method?) [message #263559] |
Fri, 23 July 2004 14:56 |
Eclipse User |
|
|
|
Originally posted by: mark.melvin.dspfactory.com
Hi All,
I was hoping to get some advice here. I am providing a branded Eclipse
as a product, and I was wondering what the best method of deploying
dependent .dll's would be. We have some C++ libraries providing
funtionality and an API has been created and wrapped with JNI resulting
in a JAR file and a corresponding .dll. I have made a general
plugin/fragment identical to the way the SWT plugin works, and my
plugins can import and use the API methods, etc.
However - the JNI wrapper calls two or three *other* .dll's and simply
including them in the same directory (my.wrapper.plugin/os/win32/x86)
does not work. I get the standard java.lang.UnsatisfiedLinkError when
my JNI .dll tries to find its dependent .dlls.
What is the best way to handle this sort of thing? I was thinking of
having a general /lib folder in our eclipse install, and adding that to
the system path. Is there any way to have Eclipse append to the system
path automatically on startup, or should I rely on a batch file? Or am
I missing the big picture, and is there a better way?
Thanks,
Mark.
|
|
|
Powered by
FUDForum. Page generated in 0.09858 seconds
Home