Re: Compile Errors with Carbon Versu BSD Dynamic Library
Re: Compile Errors with Carbon Versu BSD Dynamic Library
- Subject: Re: Compile Errors with Carbon Versu BSD Dynamic Library
- From: Chris Espinosa <email@hidden>
- Date: Tue, 12 Jul 2005 10:17:37 -0700
On Jul 12, 2005, at 6:42 AM, Mike Jackson wrote:
Figured out that "check" is already defined somewhere in Carbon.h or
the files that it includes. So I used a #undef check just after the
#includes and now it seems to compile.
yes, that would be our good friend AssertMacros.h. Another approach is
to pre-define the include guard __ASSERTMACROS__ before #including
<Carbon/Carbon.h>, and that will give you back "verify", and "require"
as well.
On a related note, is there a compile time "#def" that I can evaluate
against to figure out if I am compiling against the Carbon libs or
should I just define my own in this particular build configuration?
You can always check for definition of __CARBON__, the include guard
for <Carbon/Carbon.h>.
Chris
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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