site_archiver@lists.apple.com Delivered-To: Cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=coriolis-systems.com; h= subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=aug07; bh=5Q996EmnDFj5v1pr14ozAS0TUEA=; b=DhT63AZicBvcBI/Ub1aTRMifpn1I j4APrsGFI/kQjCt4XekL2uvKpbD0dhH0DfzCE0wydBjQXxBpAAUVtzo1mnhd6ckQ iXv8/J3s2AfKuVNpa/H5wG/zL/JRJ6x+05+CHUqcUizD7VCx1n+k/dUYD2GWSjuv RtLYxmHLfjOZj7k= On 31 May 2010, at 22:23, Jean-Daniel Dupas wrote:

Le 31 mai 2010 à 20:50, Rafael Cerioli a écrit :

...

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 ?

With libstdc++, you need to make sure you're using the g++ driver rather than gcc, otherwise you will indeed need to manually link it.

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.

Ah, OK :-) I hadn't appreciated Apple had done it that way, but since you can't really use ObjC without Foundation (unless you write *all* your own classes, obviously), it makes sense I suppose. Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ 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/site_archiver%40lists.apple... This email sent to site_archiver@lists.apple.com