• 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 makes easy things hard...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode makes easy things hard...


  • Subject: Re: XCode makes easy things hard...
  • From: John Mikros <email@hidden>
  • Date: Thu, 21 Oct 2004 17:06:31 -0700

Have you tried adding a Header Search Path to boost to the project settings (or the style settings)?

-john

On Oct 21, 2004, at 4:59 PM, George van den Driessche wrote:

Hi folks,

Let's suppose I set up a Carbon Dynamic Library project, and now I want to include some Boost headers in my C++. How on earth do I do this? I've read the documentation till I'm blue in the face and nothing I've tried works. How do I add the Boost header hierarchy to either XCode itself, or the project, so that when I write

  #include <boost/array.hpp>

in a C++ file in my project, it actually finds that header?

I just can't figure it out. It can't be so difficult, can it? I've tried setting up a source tree and adding the Boost hierarchy relative to that, and if I then get Info for array.hpp it shows

  Path: boost/array.hpp

So what else do I need to do to make this work? I can't believe that nobody else has ever set it up. I asked roughly this question three weeks ago, but the only response I got was from someone else with a similar problem, asking for an answer. Any help on this would be much appreciated, since otherwise it's going to be time to install Eclipse. Bonus points for showing me up as an idiot/neophyte by showing me the documentation that I overlooked :)

Cheers,
George

On 2 Oct 2004, at 16:14, George van den Driessche wrote:


Hi,

I'm trying to bring some code originally developed under Windows across to OSX, using XCode 1.5. There is a main target project and a couple of libraries; here's a subset:

Library A
---------
g
+-cont
  +-string.h

Executable B
------------
(Depends on Library A)
main.cpp:
  #include <Carbon/Carbon.h>
  #include <g/cont/string.h>
...

I've set up a Source Tree path to point to Library A. I created a target for the executable and added Library A's path to the External Frameworks and Libraries group.

Now, when I try to compile main.cpp, something from within Carbon.h is trying to include <String.h> (i.e. the standard C library header) but is instead picking up g/cont/string.h. This happens regardless of whether Library A is referenced using an absolute path or the Source Tree path I set up. Is this the same problem that used to exist in CodeWarrior, where specifying an include path meant recursively specifying every subdirectory in it? If so, how does one solve it?

I tried adding folder references for Library A instead of groups, but then I find that main.cpp can't find g/cont/string.h at all.

I think that in short my question is: how can I reference Library A from Executable B in such a way that
#include <g/cont/string.h>
works, and
#include <string.h>
includes the standard library header and not g/cont/string.h?


I've searched the XCode documentation for several hours on this topic, and Google too, and I've found nothing on the subject. Maybe I should switch to Eclipse...

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


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden

_______________________________________________ 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: 
 >Dumb include path/groups/folder references problem (From: George van den Driessche <email@hidden>)
 >XCode makes easy things hard... (From: George van den Driessche <email@hidden>)

  • Prev by Date: RE: Accessing static library built into framework
  • Next by Date: Re: XCode makes easy things hard...
  • Previous by thread: XCode makes easy things hard...
  • Next by thread: Re: XCode makes easy things hard...
  • Index(es):
    • Date
    • Thread