Re: Question about dynamic and static libraries
Re: Question about dynamic and static libraries
- Subject: Re: Question about dynamic and static libraries
- From: Ladd Van Tol <email@hidden>
- Date: Wed, 28 Dec 2005 23:12:00 -0800
On Dec 28, 2005, at 6:53 PM, Bill Northcott wrote:
Deprecated usually means we can still use something but that it is
going away in the future. I'm very surprised to hear that
something as useful as static libraries are going away. It is like
oatmeal being deprecated or something.
They are not needed. So Apple tools like Xcode don't support
them. You can use them as long as you stay inside the ./configure/
make/make install build method.
This is not at all true. There are plenty of cases where one would
desire a static library. For example:
1. If you're pulling in an auto-conf'ed lib, but wish to dead code
and symbol strip it for your built product. If you're operating under
a size constraint, this can become important
2. If you're building a command line tool that needs an auto-conf'ed
library, and you don't want to spray dylibs all over the system
3. If you don't want to spend a lot of time fooling around with
frameworks and install paths
4. If you have a case where the performance of calling functions in
your library is important
Remember: your use case is not the same as everyone else's.
- Ladd
_______________________________________________
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