Re: Cross-development: "mismatching weak references"
Re: Cross-development: "mismatching weak references"
- Subject: Re: Cross-development: "mismatching weak references"
- From: David Catmull <email@hidden>
- Date: Wed, 4 May 2005 14:46:21 -0700
On May 4, 2005, at 2:05 PM, Chris Espinosa <email@hidden> wrote:
You can use otool on the library and/or the app's .o files that refer
to HISegmentView to see exactly how they are expecting to import the
HISegmentView symbols. They must match.
We have no code in the application itself that uses segment views.
Actually, we do now, as part of a hack workaround I discovered: add a
file to the application project that calls the needed HISegmentedView
functions, in a function that isn't used anywhere. With that, the
mismatch errors go away. I'd like to find a prettier solution though.
Also, just root around in the sources and make sure you don't have
your own private definitions of the HISegmentView APIs anywhere that
you may be picking up. If they don't have the proper Availability
Macro then they won't be marked weak.
There is a custom version of HIToolbox.h for our CodeWarrior project
(as part of some CFM/Mach-O glue code), but it shouldn't be getting
used in the XCode project. If it were, I'm sure there would have been
errors because the custom version is based on the HIToolbox.h from
10.2 which doesn't have the item view event constants.
--
David Catmull
email@hidden
http://www.uncommonplace.com/
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