>>>If a .dll depends on another .dll, then it must be found in the
>>>system-specific, on Windows the Path (on *nix, LD_LIBRARY_PATH
>>>usually).
>>
>>
>> So to be platform "independend" you use both?
>>
>>
>>
>>
>>
>> Jan
>
>What version of Unix are you running that loads DLLs? :)
W
[EMAIL PROTECTED] wrote:
If a .dll depends on another .dll, then it must be found in
the system-specific, on Windows the Path (on *nix,
LD_LIBRARY_PATH usually).
So to be platform "independend" you use both?
Jan
What version of Unix are you running that loads DLLs? :)
-
>If a .dll depends on another .dll, then it must be found in
>the system-specific, on Windows the Path (on *nix,
>LD_LIBRARY_PATH usually).
So to be platform "independend" you use both?
Jan
-
To unsubscribe, e-mail: [
Maybe try forking the java task and using an sub-element with it? Using
the tag you can set environment variables for the forked process where
the JRE runs. My other suggestion would be to distribute the DLL with the
Java library which may or may not make more sense depending on your
situatio
>I would like to use ant to launch a java application that
>loads a black box .dll under Windows.
>Whatever the reason, the .dll path need to be present in the
>PATH environment variable.
>Otherwise, the java app fails to find and load the library.
e.g. using SWT ...
>As I need to deploy the a
