RE: Relative paths for headers
RE: Relative paths for headers
- Subject: RE: Relative paths for headers
- From: "Greg Norz" <email@hidden>
- Date: Wed, 4 Jan 2006 11:56:47 -0600
- Thread-topic: Relative paths for headers
| >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.
|
| The only problem with that (and that is what I do), is that
| it makes "clean builds" harder to do - there is setup that
| must be done before you can build your project on a new
| machine. (No more just "p4 sync; xocdebuild foo"
Will Xcode pick up on environment vars defined in a .profile or
something? That would be nice so setup could be done outside of the dev
tool and possibly just passed around as a single shell file.
Just a thought...
greg norz
southwest airlines || southwest.com
email@hidden
Wright is Wrong! - www.setlovefree.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