|
On May 21, 2008, at 10:59 AM, Michael Stauffer wrote:
In
the past, I've used ~/.MacOSX/environment.plist to set user environment vars
per Apple's instructions. I like to set some environment vars to source
paths that change sometimes, and then expand them in Xcode's project
settings. It's all worked fine in the past, until I installed Leopard. It
simply seems that environment.plist is not being loaded, because I don't see
my env vars in the shell's list of env vars after logging in. Needless to
say, Xcode doesn't see them either. I've tried both using the plist file I
used on 10.4.11, and creating a new one, and also tried two different
accounts. Same problem.
Only thing
unusual on my system is that one of the two accounts I have has a home dir
that's on a different partition, and symlinked from /Users. It seems to be
working fine, and I've always done that in the past. The other account I
tested has its home folder in the regular place, on the startup
partition.
I think you're saying that both these accounts have the same problem,
right? So that would mean the symlink is not the cause and still (so far
as we can tell) works as well as ever.
Thanks for the
reply. Yes, that's right. Symlink does not seem to be the
problem.
I can
create a shell script to set the vars and load xcode, and that works, and I
suppose I could create a .bashrc script(?), but it bugs me that I can't get
environment.plist working. Anyone have any suggestions? Many
thanks.
Scripts and .bashrc's won't help get the vars set when you launch Xcode
via double-click; you really want that plist working again.
Yeah, for
now I'm also launching xcode from the script where I export env vars and it
works.
You don't mention whether you've checked file and directory permissions. You don't mention whether you've checked Console for messages during log-in. You don't mention whether you've checked the file itself to be sure it hasn't been damaged somehow.
FWIW, my environment.plist is still working fine: this is not some
general Leopard bug (though it might still be some Leopard bug that's
triggered by something unusual in your set-up).
Permissions look fine. .MacOSX/ is 755, and
environment.plist is 644. I've tried with both a copy of the file, and by
creating a new one using plist editor. I checked the console but don't see any
msgs regarding this file.
Yeah, doesn't seem like a general bug, since
while looking around I saw it was working for other folks.
-Michael
|