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 ...
If it ever happens again, please tell us and file a bug, then.
Fiddling with command line flags in Xcode shouldn't be the 2006 way
of linking.
As a small test shows, adding the library to the project results in
exactly an "-lz" flag added to the gcc/linking invocation. Same
result, less error prone.
_______________________________________________
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
