[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Accessing PATH Environment Variable
|
Just my two cents. I'd prefer to see build integrations not depend on the
PATH environment variable. I've certainly seen cases where a user wants to
use different toolchains at different times and, for whatever reason, can't
put all of them in their path.
I think it would be just a cleaner user experience for Eclipse to manage the
paths for their toolchains for them. That's what I'm doing with the Windows
SDK and MinGW integrations I'm working on.
Off soapbox...
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC Member
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of wieant@xxxxxxxxx
> Sent: Thursday, February 08, 2007 3:31 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Accessing PATH Environment Variable
>
>
> >> This may be a dumb question, but why can't you use
> System.getenv("PATH")?
>
> > In Sun's 1.4 jre this is how its implemented;
> >
> > public static String getenv(String name) {
> > throw new Error("getenv no longer supported, use properties and -D
> > instead: " + name);
> > }
>
> Strangely enough in 1.5 it is undeprecated again (and seems to work to get
> the PATH environment variable), see
>
> http://java.sun.com/j2se/1.4.2/docs/api/java/lang/System.html#getenv(java.
> lang.String)
> versus
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#getenv(java.
> lang.String)
>
> Yet another reason to switch to 1.5 :-)
>
> Regards,
> Wieant
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
