Re: Anyway to default Xcode to use relative paths?
Re: Anyway to default Xcode to use relative paths?
- Subject: Re: Anyway to default Xcode to use relative paths?
- From: Eric Eizenman <email@hidden>
- Date: Mon, 6 Jun 2005 10:20:24 -0700
I was looking for the same thing. The answer was that it's possible
with Xcode v2, but not previous versions.
I'm still using v1.5, so I didn't get to verify this.
On Jun 4, 2005, at 6:35 AM, Mark Munz (DevList) wrote:
Is there anyway to default Xcode to use relative paths, particularly
when adding frameworks?
It seems that whenever I add a new framework, Xcode puts a hard-coded
path to the location, even though I already relative path to the
location. For example I have a setup like this:
ProjectFolder
MyProject.xcode
MyFrameworks/
First.framework <-- added earlier (setup relative path to
it)
Second.framework
In the target Build settings, I have "$(SRCROOT)/MyFrameworks" in the
Framework search paths. If I go and add another framework from that
same folder (like Second.framework), it will insert a
/Volumes/VolName/ProjectFolder/MyFrameworks/ path into the build
location (even though it's already in there in relative form).
It would seem to me, that if the framework being added is below the
project file, it should assume it is relative to the project. It would
also seem to me that Xcode could verify that the path isn't already
defined before adding it.
Is there a way to override this default behavior?
Thanks.
Mark Munz
------------------------------------------------------------------
Eric Eizenman
BIAS Inc., Audio Software Development
------------------------------------------------------------------
_______________________________________________
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