Re: Converting Xcode paths to usable paths
Re: Converting Xcode paths to usable paths
- Subject: Re: Converting Xcode paths to usable paths
- From: Steve Mills <email@hidden>
- Date: Tue, 01 Dec 2009 16:14:47 -0600
On Dec 1, 2009, at 15:55:25, Chris Espinosa wrote:
> 1) The first path is a real Posix path.
Yes, it's real, but not all software (including lots of Apple software) can handle it.
> 2) It has the ../../.. in it because you defined something with a path relative to another path, which is not a direct ancestor of that path. In this case, it looks like your Per-Configuration Build Directory is defined relative to the Project Directory (I'm supposing that's what C2Mac is) but is actually outside the Project Directory. If you make it an absolute path or a child of the Project Directory you won't get the chain of ../../.. references.
It can't be an absolute path - our projects are checked into source control - and it needs to be outside of the project dir because a bunch of subprojects are included in the project, and they all need to use a common build dir due to some limitation in Xcode/gcc (which I no longer remember). The .. stuff needs to be fixed. I see problems caused by ".." being in a path all the time, like right-clicking a window's titlebar and choosing a dir in the path popup, or drag & dropping a file from an Xcode project (or a window's proxy icon) to Terminal and having the ".." path appear, then that path not being something that p4 understands.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.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