Re: Relative paths for headers
Re: Relative paths for headers
- Subject: Re: Relative paths for headers
- From: Chris Espinosa <email@hidden>
- Date: Wed, 4 Jan 2006 09:36:56 -0800
On Jan 4, 2006, at 9:23 AM, Greg Norz wrote:
with the "boost" directory and it's files inside. In order to do this
in
Xcode, from where does the project setting "User Header Search Paths"
start? From the location of the .xcodeproj file? From the location of
the individual source files that need a particular include?
If relative paths don't work in Xcode, what are some other developers
using when they share projects across multiple machines that might
house
code in different locations on disk?
In general it's unwise to rely on "unrooted" relative paths in UNIX,
that is, to trust in a particular setting of the current working
directory.
The two ways to deal with this are to use built-in build settings or
source trees.
Your project wrapper is in the directory pointed to by $(SRCROOT), so a
proper path would be $(SRCROOT)/../../common/include, for example.
The better way would be to define BOOST in your per-user Source Trees
Xcode preference pane to point to Boost on your disk, and have
everybody in the project team do the same. Boost need not be in the
same place on each machine. Then add a user header search path to
$(BOOST)/common/include and then the project will find the right
headers on any machine that has BOOST defined to point to the correct
Boost installation.
Chris
_______________________________________________
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