Eclipse Community Forums: Java Development Tools (JDT) » Path variables in debug launch configuration

Home » Language IDEs » Java Development Tools (JDT) » Path variables in debug launch configuration

Path variables in debug launch configuration [message #101783]

Mon, 06 October 2003 15:45

Eclipse User

I am attempting to convert a number of local debug launch configurations
into shared launch configurations. Part of the process involves removing all
hard coded paths. I am having a problem with specifying the VM arguments.

My original configuration had the following parameters to allow access to my
JNI DLL's.

-Djava.library.path=E:\cryptoroot\Release_6_Development\src\ cpp\libraries\jR
egistryKey\jregistrykey.dll\debug;
E:\CRYPTORoot\Release_6_Development\src\cpp\libraries\jpcsc\ debug

This specification worked.

I then changed to use
-Djava.library.path=PPATH\cpp\libraries\jRegistryKey\jregist rykey.dll\debug;
PPATH\cpp\libraries\jpcsc\debug

where PPATH is a path variable that is set to the root of my source tree for
each workspace where the launch configuration will be run. Unfortunately
with this specification, the JNI DLL's are not found.

My question is - is this a legitimate use of path variables, and if not how
should I approach the problem of removing these hard coded paths?

Regards

Jonathan Gossage

Re: Path variables in debug launch configuration [message #101810 is a reply to message #101783]

Mon, 06 October 2003 16:37

Eclipse User

VM/Program args to do not (yet) support the use of variables. It is a
planned feature in the 3.0 release.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=10035

Darin

"Jonathan Gossage" <jonathan@cryptocard.com> wrote in message
news:blsgqp$ked$1@eclipse.org...
> I am attempting to convert a number of local debug launch configurations
> into shared launch configurations. Part of the process involves removing
all
> hard coded paths. I am having a problem with specifying the VM arguments.
>
> My original configuration had the following parameters to allow access to
my
> JNI DLL's.
>
> -Djava.library.path=E:\cryptoroot\Release_6_Development\src\ cpp\libraries\
jR
> egistryKey\jregistrykey.dll\debug;
> E:\CRYPTORoot\Release_6_Development\src\cpp\libraries\jpcsc\ debug
>
> This specification worked.
>
> I then changed to use
> -Djava.library.path=PPATH\cpp\libraries\jRegistryKey\jregist rykey.dll\debu
g;
> PPATH\cpp\libraries\jpcsc\debug
>
> where PPATH is a path variable that is set to the root of my source tree
for
> each workspace where the launch configuration will be run. Unfortunately
> with this specification, the JNI DLL's are not found.
>
> My question is - is this a legitimate use of path variables, and if not
how
> should I approach the problem of removing these hard coded paths?
>
> Regards
>
> Jonathan Gossage
>
>

Previous Topic:	JDBC problem: Couldn't load ocijdbc8.dll
Next Topic:	Tell is app in running in debug?

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 21:13:53 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter