Re: Availability Macros, errors in cocoa headers?
Re: Availability Macros, errors in cocoa headers?
- Subject: Re: Availability Macros, errors in cocoa headers?
- From: "Sean McBride" <email@hidden>
- Date: Fri, 31 Dec 2004 00:40:53 -0500
Ricky Sharp (email@hidden) on Thu, Dec 30, 2004 07:08 PM said:
>Also reproduced it here (10.3.7, Xcode 1.5). The animationEffect param
>is of type NSAnimationEffect. But that type is only defined if
>MAC_OS_X_VERSION_MAX_ALLOWED >= MAC_OS_X_VERSION_10_3.
Thanks for confirming my sanity :)
>Definitely file a bug about this as there should be some mechanism in
<rdar://3936074>
Well, at least things compile with -DMAC_OS_X_VERSION_MIN_REQUIRED=1020 -
DMAC_OS_X_VERSION_MAX_ALLOWED=1030.
But I still can't get my app to launch on 10.2. :( I use several 10.3-
only things (bindings notably) but would like to at least get to main()
on 10.2 then bring up a Carbon alert. I'm willing to forget about 10.0
and 10.1.
Shouldn't setting the above macros automatically weak link things that
need to be?
In 10.2 I see this in Console:
objc: failed objc_getClass(NSValueTransformer) for
PLWhenToStringTransformer->super_class
objc: please link appropriate classes in your program
Ack!
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Mac Software Designer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden