The problem was that Xcode wouldn't add the symbolic link /usr/lib/libz.dylib, but would add what the link pointed to instead. This was a convenient way of ignoring the purpose of symbolic links for all those who believe that symbolic links shouldn't exist. I believe that this is no longer occurring, but it's worth keeping an eye on it. The danger is that the app will fail to run on a system that has a different version of libz if the symbolic link is followed at build time.
Will
----- Original Message ----
From: Uli Kusterer <email@hidden>
To: Markus Hitter <email@hidden>
Cc: Cocoa Cocoa-Dev <email@hidden>; David Chan <email@hidden>
Sent: Tuesday, February 14, 2006 6:47:54 AM
Subject: Re: Using zlib for i386 (or Universal) builds on PPC clients
Am 14.02.2006 um 11:21 schrieb Markus Hitter:
> Am 14.02.2006 um 02:32 schrieb David Chan:
>
>> Oh ya.. that -lz works perfectly.
>
> A more Xcode'ish way would be to add the library to the project,
> just like you'd add a source file or a framework. Then, Xcode takes
> care to add the right flags. Same for -I flag/headers.
I'm not sure those two are fully equivalent. I seem to remember
some cases where the -lsomething flag was actually doing something
smarter than when you added a library ... was it relevant for
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
