Re: Undefined lookup, ObjC, and 64-bit
Re: Undefined lookup, ObjC, and 64-bit
- Subject: Re: Undefined lookup, ObjC, and 64-bit
- From: Jean-Daniel Dupas <email@hidden>
- Date: Mon, 12 May 2008 21:31:24 +0200
Unlike the 32 bits runtime, the 64 bits runtime respects class symbols
visibility.
If you do not export the class symbol, you cannot use it from an other
binary (just like with C or C++ functions and classes).
Actually, I'm conditionnaly using the folowing attribute to solve this
issue (IIRC the compiler raises an error if you use with a class
symbol on 32 bits arch).
__attribute__((visibility("default")))
You can use 'nm' on your bundle to make sure this is the cause of this
error.
Le 12 mai 08 à 20:14, Ken Thomases a écrit :
On May 12, 2008, at 12:39 PM, Nick Zitzmann wrote:
2. How do I fix this without building the abstract superclass into
each bundle (which is wasteful)?
This isn't my area of expertise, but isn't this the purpose of the -
bundle_loader linker option?
-Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden