Re: [Wrapper-user] Problems with loading DLL from other DLL

[Leif M. <le...@ta...>]

Michael,
    I have had this same problem in the past.  As Michael said it is a 
matter of setting
up your PATH environment variable correctly.  In my case, all of the 
DLLs were in
my application's lib directory.  Add something like the following to 
your wrapper.conf
file:
set.PATH=..%WRAPPER_FILE_SEPARATOR%lib%WRAPPER_PATH_SEPARATOR%%PATH%
wrapper.java.library.path.1=../lib

    You could also do the following, but the first makes it cross 
platform compatible.
set.PATH=../lib;%PATH%
wrapper.java.library.path.1=../lib

Cheers,
Leif

Jim Redman wrote:

> Michael,
>
>
> Michael Trompertz wrote:
>
>> Hello
>>
>> I have problems with a DLL, which loads another DLL on a windows 
>> system. The
>> second DLL is not in the environment path of windows to seperate my
>> installation from other installations.
>> The first DLL is found via the wrapper.java.library.path but the 
>> second is
>> not found although it is in the same directory.
>>
>> Any ideas?
>
>
> The second dll by default follows the standard rules for Windows 
> loading.  That is it has to be on the environment path (not the 
> classpath or the library path the real Windows path).
>
> This implicitly always includes the current directory, that is, the 
> directory that the application starts from.  So this may be the 
> easiest place to put it if you want some separation.
>
> There are some other choices.  Immediately I can think of these.  You 
> could put your directory on the environment path by modifying the 
> wrapper code, or you could explicitly load the second dll.
>
> Jim
>