Date: Tue, 21 Feb 2006 08:54:22 -0500
From: Stephen Chu <email@hidden>
Subject: Re: Source trees don't work any more
To: xcode-Users List <email@hidden>
On 17 Feb 2006 20:25:1, Chris Espinosa wrote:
On Feb 17, 2006, at 3:47 PM, Stephen Chu wrote:
WTF is going on? I have the source trees working even after
upgrade to 2.2. I have to add a new one and all the existing paths
are escaped. Now none of the paths work and needless to say, none
of my projects works.
What is it with Apple? Do they even have a clue? Yes, I am pissed.
Did you read the Xcode 2.2 Release Notes, Known Issues and
Workarounds, where it says:
"Spaces in Project Path Items
Any build setting that contains a path (or includes another build
setting that resolves to a path) must be enclosed in double quotes
if the path is likely to contain a space character. Xcode will
handle the quoted value correctly, but will fail if an unquoted
value resolves to a path that includes a space."
Chris,
I am not sure we are talking about the same thing. The issue here is
not XCode's handling of spaces in paths used in source code files.
It's it's insistence on escaping spaces in source tree paths. Quoted
or not, it changes all space characters in source tree paths to '\ '
and all source files in the project that are specified relative to
the trees are now missing.