Dominique Devienne wrote:
On 1/10/06, [EMAIL PROTECTED] [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?
java
env value=${thePath}
[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?
java
env value=${thePath} key=PATH/
env value=${thePath} key=LD_LIBRARY_PATH/
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?
java
env value=${thePath} key=PATH/
env value=${thePath} key=LD_LIBRARY_PATH/ /java
Jan
What
On 1/10/06, [EMAIL PROTECTED] [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?
java
env value=${thePath} key=PATH/
env
As I need to deploy the app on numerous machines, I'd rather
avoid to set the PATH each time.
Any idea to set the environment within ant commandline or even
better within the ant file before I call the java task?
try setting the java.library.path system property.
There are 2 ways to find
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?
java
env value=${thePath} key=PATH/
env value=${thePath} key=LD_LIBRARY_PATH/
/java
Jan
Hi,
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.
As I need to deploy the app on numerous
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 app on
Maybe try forking the java task and using an env/ sub-element with it? Using
the env/ 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
