Re: Source trees don't work any more
Re: Source trees don't work any more
- Subject: Re: Source trees don't work any more
- From: Stephen Chu <email@hidden>
- Date: Tue, 21 Feb 2006 08:54:22 -0500
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."
We know it's a problem; it was introduced by work we did to reduce
merge conflicts in project files. We are working on a fix, but
won't roll out one until we find a technique that's both reliable
and backwards compatible with the existing 2.2 behavior. For now,
providing paths that look like
"$(MOREFILES)/MoreFilesX/"
is the most reliable way.
If you need to bulk-change paths like this, you can open the
foo.xcodeproj/project.pbxproj file in TextEdit, BBEdit, etc. and do
search-and-replace rather than use the target inspector to add this
quoting. (I always recommend making a backup of your project file
before hand-editing it.)
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.
Again, the file CAN NOT BE FOUND anymore. They are in RED in the
project source list. The only way I can fix it is to rename all the
folders in all the source tree paths to not having spaces. But that's
not possible for the files are SHARE with other platform and projects.
I don't understand keeping spaces in source trees as I type them in
can be such a pain. If that cause some conflict, then people with the
conflict can easily type in the path in escape form! Now people like
me have NO CHANCE of making it right. And if the paths in source
trees have to be stored in space-escaped form, than make the the
other part of the same application AWARE of it. Damn it.
Why do I always have the feeling that XCode will go the extra mile
just to make things difficult?
--
Stephen Chu <mailto:email@hidden>
Rampage Systems, Inc. <http://www.rampageinc.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden