Re: Xcode 3.1 and boost
Re: Xcode 3.1 and boost
- Subject: Re: Xcode 3.1 and boost
- From: Frank van Meurs <email@hidden>
- Date: Wed, 23 Jul 2008 11:55:04 +0200
On Jul 23, 2008, at 9:37 AM, Paul Walmsley wrote:
The problem seems to be locating some additional files nested
inside of boost. I’ve updated the build setting “Header Search
Paths” to point to “../boost” and the boost directory itself is
located at the same level as the rest of my sources. I’ve also
tried setting “User Header Search Paths” to point to “../boost” but
had no luck there either. Hard coding the path to boost doesn’t
work either and is not a solution I’m content to settle with anyway.
I suspect that this has arisen because you have your code arranged
in several subdirectories but you use '../boost' as a relative
header search path. So when boost files themselves try to include
other files they look in '../boost' relative to their own path. To
fix this try setting the include path to $(SRCROOT)/boost instead,
which makes the paths relative to your project (so in effect the
compiler sees it as an absolute path)
What I have done is set the "Header search path" and "Library search
path" variables to "/macports/local/include" and "/macports/local/
lib", which in your case would probably resolve to "/opt/local/
include" and "/opt/local/lib", and subsequently referenced boost
headers through "#include "boost/assert/hpp"". So, I set my optional
search paths to the respective boost locations and reference the
headers through use of a subdirectory.
Frank _______________________________________________
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