Thank you. As you suggested, responses
from the CMake mailing list also asks me to check environment vars. On my
machine:
Cat ~/.bash_profile
Export PATH=/usr/local/bin:$PATH
Echo $PATH
/usr/local/bin:bin:/sbin:/usr/bin:/usr/sbin
Cat ~/.MacOSX/environment.plist
No such file or directory
Thus I am unsure where CMake is getting that
erroneous ‘/Develeper/SDKs/MacOSX10.4u.sdk’ directory, and hope more info can
be found from the Xcode community.
I use cmake-2.6.1-Darwin-universal on OSX
10.4.9
From: Chris Espinosa
[mailto:email@hidden]
Sent: Wednesday, September 10,
2008 1:37 PM
To: Bo Huang
Cc: email@hidden
Subject: Re: Xcode environment
variables
On Sep 10, 2008, at 9:57 AM, Bo Huang wrote:
Which environment variables
does xCode or the developer package set?
I use a tool CMake to build; it always
picks up ‘/Develeper/SDKs/MacOSX10.4u.sdk’ as a c++ include path. Notice the
incorrect spelling for Developer.
I did not set that when installing CMake;
this value probably exists some where in my OS.
But, I tried ‘set’ and ‘env’ in a command
line and do not see any similar value.
I tried uninstalling xCode, restart
system, and reinstall. Still doesn’t work.
It's not clear what context you're talking about.
Installing Xcode (note capitalization), doesn't set or change any
environment variables in your user login or any shell configuration files.
When you use Xcode itself, it sets a vary large number of environment
variables when it invokes tools and scripts during an Xcode build, but it does
not affect anything outside the context of things built using Xcode.
So it looks like you have some misconfiguration in your CMake files or
in your own shell configurations, or (less likely) in your ~/.MacOSX/environment.plist file (if you have one).