Re: Question about dynamic and static libraries
Re: Question about dynamic and static libraries
- Subject: Re: Question about dynamic and static libraries
- From: Thomas Engelmeier <email@hidden>
- Date: Tue, 3 Jan 2006 00:42:43 +0100
You get the same behavior for calls into that lib *all the time*,
even across OS platforms, and not some hard reproducible support
call because user installed rev x.y of that .dylib by the means of
dports et al.
If you include _your_ private snapshot of that library as .dylib
in you app, chances are you loose diskspace - with a dylib there
is no chance the linker can strip e.g. most of the libtiff code
because it is only used to embed an color profile tag into DNG files.
The linker has a chance, even with dynamic libraries.
So instead of filing a Radar about poor static library handling,
filing one for stripping dylibs for specific application use? Just
the way the linker would do it with static libraries?
That would be completely against the "nature" of a dylib. A dynamic /
shared library is intended to be used by an arbitrary number of
unrelated binaries, so striping symbols does not make any sense.
Regards,
Tom_E
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden