Re: Adding frameworks to a project - adding corresponding search paths to find the headers. Necessary?
Re: Adding frameworks to a project - adding corresponding search paths to find the headers. Necessary?
- Subject: Re: Adding frameworks to a project - adding corresponding search paths to find the headers. Necessary?
- From: Eamon Ford <email@hidden>
- Date: Mon, 5 Nov 2007 18:58:11 -0800
I have exactly the same problem. I just discovered it last night.
On Nov 5, 2007, at 6:53 PM, Mike Throckmorton wrote:
Up until today, I could have sworn that if I added a framework to a
project, a resultant build would find references to the headers of
said framework without me having to add a search path in project (or
target) settings.
But it seems I had to. (CoreServices.framework: Including
<CoreServices.h> or embedded headers like CarbonCore.h in source
files in the project and Xcode failed to find the headers).
I guess it is still a mystery to me what things I have to explicitly
point Xcode projects at to have Xcode find them, and what things it
seems to find by magic.
Is there someplace this is explained so I can, like, predict what I
am going to have to add or not add (to search paths)?
-----------------------------------------------
Mike Throckmorton email@hidden
Software Engineer
My Mac running Mac OS X has been up 5 days,
running Mac OS X and it's starting to drift.
_______________________________________________
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:
This email sent to email@hidden