RE: [cdt-dev] Environment variables not passed to make

["Brad Jarvinen" <Brad.Jarvinen@xxxxxxxxxxxxxx>]

Leo,

A few questions about added functionality for dealing with environment
variables:

- Is there a design document yet for this functionality you mention?
- Is the bugzilla number tracking this issue 80905 or is another one
being used?
- Is this still a 3.0 thing or is it pushed out?

My problem I'm interested in is 80905 in which gcc is assumed to be in
the environment variable PATH.  

Thanks,
Brad

 

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Treggiari, Leo
Sent: Tuesday, February 22, 2005 1:04 PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Environment variables not passed to make

Yes, the environment of the Eclipse process should be passed to the
build process.  You should make sure that your PATH is set up as
expected in the environment that invokes Eclipse.  For CDT 3.0, we plan
on adding additional functionality for dealing with environment
variables.  There should be a design document in mid-March.

Regards,
Leo

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Craig Rasmussen
Sent: Tuesday, February 22, 2005 3:56 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Environment variables not passed to make

Are environment variables supposed to be passed to make in the managed
build environment?  I have created a toolchain for a Fortran compiler,
but I have to explicitly add the path to the compiler in the properties
page because my PATH variable is not used.

Is this a bug?

Thanks,
Craig

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev