• 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: Adrian Milliner <email@hidden>
  • Date: Sun, 24 Oct 2004 09:34:49 +0100

Actually, setting it up in Target info is more general.

Generally, you have one Target and at least two build styles (dev+deploy) in the Project Info.

To set a header path used by both build styles of the project, set it in the Target info.

From the docs:

"The build setting values in a build style have higher precedence than those in a target. If a build setting is assigned different values in the active build style and in the active target, the value in the build style overrides the value in the target. Xcode indicates this by crossing out settings that are overridden by the active build style."

But I agree, with the original poster; this is much more complicated that it needs to be and Xcode obfuscates rather than illuminates IMO.

On 23 Oct 2004, at 18:29, George van den Driessche wrote:


On 22 Oct 2004, at 01:07, Jeff Laing wrote:

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'm guessing you're facing the same problem I did.

The frustrating thing about XCODE is that it has some idiotic defaults
hidden behind innocuous GUI widgets.

If you select, in the left-hand browser, the TARGET you want to build, then
press the (I) icon, you get a tabbed editor window. On one of the tabs
there is a list of name,value pairs which for me was a very short list that
wasn't helpful.


It took me forever to realise that there is a little popup menu in the top
of the list which, if you click it, shows that there are a zillion other
options. One of those specifies "include search paths" or some such.

Thank you for your help, as a result of which it took me slightly less than forever to find this menu :) Thanks also to the others who replied. It's a well-disguised menu, isn't it. Incidentally, the header search path field is available in the Project info as well as the Target info, so I guess you can set up paths for all targets simultaneously.


Cheers,
George

_______________________________________________
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: 
 >RE: XCode makes easy things hard... (From: Jeff Laing <email@hidden>)
 >Re: XCode makes easy things hard... (From: George van den Driessche <email@hidden>)

  • Prev by Date: Re: XCode 1.5, No Warning for Missing Return Value
  • Next by Date: Need langspec for XCode pblangspec files :)
  • Previous by thread: Re: XCode makes easy things hard...
  • Next by thread: RE: XCode makes easy things hard...
  • Index(es):
    • Date
    • Thread