Re: HEADER_SEARCH_PATHS problems
Re: HEADER_SEARCH_PATHS problems
- Subject: Re: HEADER_SEARCH_PATHS problems
- From: "Isaac Wankerl" <email@hidden>
- Date: Fri, 21 Jul 2006 10:30:38 -0500
On 7/21/06, Paul Walmsley <email@hidden> wrote:
> I think this is a feature needed to work around the problems Xcode used to have with spaces in search paths, and with disappearing quotation marks
> around them. I just checked in these HEADER_SEARCH_PATHS_QUOTED_1 paths
> once, and everything seems normal now.
>
> Seeing spaces/quoted paths handled like this is a bit strange to me, but I try to think of this as an internal implementation detail.
>
I've encountered this as well with spaces in path names. It is an
implementation detail, although it can be a pain when you try to edit
the paths in the project/target info panel, since it prints the new path
as $(HEADER_SEARCH_PATHS_QUOTED_1) and doesn't show you what the string
actually is. I think you have to manually edit the project.pbxproj file
to change it (which is far from ideal). Is there another way to see
and change what the value is?
Paul
Yes, not being able to edit those quoted paths without manually
changing the project.pbxproj is definitely a PITA and I'll log a bug
on that in a minute.
After looking my project again, it appears that for some reason the my
library search paths were messed up. All I did was add a 4-5
source/header files to my project and a library. I committed the
changes to perforce and the project builds fine on the original Mac,
but I checked the project out on another and the options sent to ld
did not include the search path for the newly added library (it
doubled up one of the other preexisting paths instead).
Isaac
_______________________________________________
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