• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 3.1 and boost
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.1 and boost


  • Subject: Re: Xcode 3.1 and boost
  • From: "Mastalir, George" <email@hidden>
  • Date: Wed, 23 Jul 2008 06:47:34 -0700
  • Thread-topic: Xcode 3.1 and boost

On 7/23/08 5:31 AM, "Eric Miller" <email@hidden> wrote:
> The include path should point to the parent of the 'boost' directory.
> And you should use #include <boost/scoped_ptr.hpp> in your source.
> All the boost libraries should be included this way.  It helps prevent
> file name collisions on the include path (think of it as a namespace).
> The boost libraries internally expect the include path to be set up this way.

Pointing the "Header Search Path" to the parent of the 'boost' directory
finally solved the problem. And I used $(SRCROOT)/boost--making the paths
relative to my project--as suggested by Paul.

Many thanks,

--George

 _______________________________________________
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

References: 
 >Re: Xcode 3.1 and boost (From: "Eric Miller" <email@hidden>)

  • Prev by Date: Re: Another useless warning - 'Hidden Local Variables'
  • Next by Date: Re: Gcc warning instead of error
  • Previous by thread: Re: Xcode 3.1 and boost
  • Next by thread: Problem creating a new Target
  • Index(es):
    • Date
    • Thread