• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Question about dynamic and static libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about dynamic and static libraries


  • Subject: Re: Question about dynamic and static libraries
  • From: Thomas Engelmeier <email@hidden>
  • Date: Thu, 29 Dec 2005 20:21:29 +0100

I think that several folks have articulated the many valid reasons why traditional static libraries are desireable: organization/ modularization of code within a single project by team members, use of large third party (often open source) in situations where one wishes to use a particular snapshot of the library - not as a dynamic "system resource".
All this can be done with dylibs on MacOS X. See below

It can NOT all be done with dylibs.
One point for a static lib in an product is support cost.
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.


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.

Oh yeah, we need FAAAAAAAAAAAAAAAAAAAAAT binaries are default, and they will bloat even more for two architectures. Striping unused function calls is really some undesirable luxory for those cheap folks that don't "want" to have 4 GB RAM and 250 GB drives in their Laptop. Static libs are the luxory for those cheap developers that don't want to pile one machine per OS X subrevision, security update and processor architecture in order to reproduce exact behavior at the hotline.


Mind to specify the meaning of "not needed" in an commercial environment?

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
  • Prev by Date: Re: Generating multiple localizations when creating a new project
  • Next by Date: Re: setting custom compiler
  • Previous by thread: Re: Question about dynamic and static libraries
  • Next by thread: Fwd: Question about dynamic and static libraries
  • Index(es):
    • Date
    • Thread