Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Environment variables not passed to make

Thanks Leo.  But correct me if I'm wrong but this is only applicable to managed make projects.  The problem I'd like to solve is not requiring the Cygwin/bin to be embedded in the PATH environment variable before invocation of Eclipse.  As √ėyvind mentioned in bug 80905 having the bin in the PATH can cause interoperability problems.  I'd like a solution that essentially always adds the Cygwin/bin to the PATH on any exec() command invoked from within CDT so it can find the Cygwin binaries (giving roughly something functionally equivalent of doing a set PATH=C:\Cygwin\bin;%PATH% and then invoking Eclipse in a bat file).

How about this idea:
All CDT invocations of command line tools of any significance goes through the ProcessFactory and Spawner classes.  One could patch the ProcesFactory.addPathsToEnv() method to add paths to the PATH environment variable for the exec() command invocation from a defined extension point.  The extension point could be defined for the configuration to apply to all CDT.  A preferences page for CDT could be added to allow the user to add/remove/edit paths.  To make the path in the extension point portable and not hard-coded, one could make an interface for the extension point that dynamically provides the full path values.

Thanks,
Brad


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari, Leo
Sent: Tuesday, April 26, 2005 1:13 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Environment variables not passed to make

Hi Brad,

The environment variable design for MBS is in bugzilla 88497.  The design and implementation are being done by Mikhail Sennikovsky at Intel.  He should be submitting a patch any day now with lots of good functionality...

Regards,
Leo

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Brad Jarvinen
Sent: Tuesday, April 26, 2005 4:02 PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Environment variables not passed to make

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
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top