[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Environment variables not passed to make
|
Yes, the problem is that under MacOSX, Eclipse inherits its environment
from the window manager, so setting your path in .bash_profile is
useless. You need to create a file called environment.plist and put it
in a directory called .MacOSX in your home directory.
It would be a nice feature of the Eclipse platform if you could
view/change environment variables though.
Greg
On Feb 22, 2005, at 2:03 PM, Treggiari, Leo wrote:
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
