On 5/31/05 2:00 PM, Ian Anderson didst favor us with:
> If your app is CFM, it's generally easier to use the Universal Interfaces
> which don't use framework style includes. If your app is Mach-O you'll want
> to say #include <CoreFoundation/CoreFoundation.h> (or more likely
> <Carbon/Carbon.h>) instead of just <CoreFoundation.h>. Then you'll either
> need to use MacHeaders or the following as your precomp: #define
> __NOEXTENSIONS__ #define __CF_USE_FRAMEWORK_INCLUDES__
>
> Ian
I'm curious. I use CW and have never used framework-style includes other
than this one in my prefix file:
#include <Carbon/Carbon.h>
Works fine and all, but I always wonder what the point is of framework-style
includes.
Larry
>
>
>> First, apologies if this is not the appropriate area for this post.
>>
>> I am working on a project that for reasons too numerous to go into, can not
>> currently be moved to XCode and I still need to work with it in CodeWarrior
>> 8.3.
>>
>> Long story short, I am having trouble figuring out just how to support the
>> new framework style includes. I can do a
>>
>> #include <CoreFoundation.h>
>>
>> in one of my source files. However, CoreFoundation.h has several
>>
>> #include <CoreFoundation/CFBase.h>
>>
>> and similar includes in it. These are not found correctly and the project
>> will not compile. Is there any way to set up the Access Paths in CodeWarrior
>> 8.3 to accomodate these CoreFoundation or framework style include statements
>> to get back to a compilable state?
>>
>> Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
