• 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: Static Library Equivalent of a Framework?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Static Library Equivalent of a Framework?


  • Subject: Re: Static Library Equivalent of a Framework?
  • From: George Warner <email@hidden>
  • Date: Tue, 18 Nov 2003 14:16:01 -0800

on 11/18/03 2:08 PM, Drew McCormack at <email@hidden> wrote:
> My understanding is that when you link statically, only the parts the
> library actually called by the application are included. If the library
> is big, and you only call a small part of it,
> in the static case, it doesn't matter. But if you use a dynamic
> library, you have to include all of the library code whether you use it
> or not.

This is called "dead stripping". When you statically link the linker can
ignore any code that isn't being used (directly or indirectly). With dynamic
libraries there's no way to know which routines may or may not be used so
you have to ship them all.

--
Enjoy,
George Warner,
Schizophrenic Optimization Scientists
Apple Developer Technical Support (DTS)
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Static Library Equivalent of a Framework? (From: Drew McCormack <email@hidden>)

  • Prev by Date: Re: Removing a breakpoint?
  • Next by Date: Re: CVS integration for nibs?
  • Previous by thread: Re: Static Library Equivalent of a Framework?
  • Next by thread: Re: Static Library Equivalent of a Framework?
  • Index(es):
    • Date
    • Thread