Le 31 mai 2010 à 20:50, Rafael Cerioli a écrit : > > Le 31 mai 2010 à 13:41, Alastair Houghton a écrit : > >> On 31 May 2010, at 14:03, Rafael Cerioli wrote: >> >>> I guess you need the framework libobjc.A.dylib for that stuff. >> >> 1. That's a dylib (aka DLL, aka shared object), not a framework. > > Yes I know that's not a framework, thanks for pointed that out. I only used > this term because when we add that lib to the xcode project, we go to "Add, > Existing Frameworks". > >> >> 2. Since you're using Objective-C, that library is already going to be >> linked with your program (it's the Objective-C runtime, and just like the >> C++ standard library and the C runtime, it is linked with your program >> automatically by the compiler). > > Well, that's curious. I'm surely missing a particular setting because when I > don't manually link that lib (and it's the same with libstdc++), I get link > errors. Do you know if there is a setting that controls that behavior ? > Thank you, > > Rafael
I don't think the compiler try to link on it automatically, but as it is a "subframework" of Foundation (a library marked as LC_REEXPORT_DYLIB), you usually never have to bother with it as virtually any obj-c piece of code on OS X links on this framework. -- Jean-Daniel _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com