• 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: Wrapping conventional .a libraries in a framework...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wrapping conventional .a libraries in a framework...


  • Subject: Re: Wrapping conventional .a libraries in a framework...
  • From: Brian Webster <email@hidden>
  • Date: Wed, 24 Oct 2001 20:11:29 -0500

By default the linker won't load the symbols from a static library unless they are explicitly needed. You can force the libraries to be loaded by using the -u option when linking, which enters a symbol name into the linker as being undeclared. Pass in -u and a symbol name (any symbol name will do) from your static library and ld should load and link the library. For two libraries, you'll have to do this twice, using a symbol from each library. You can add these flags in Project Builder in OTHER_LDFLAGS in the Build Settings pane.

On Wednesday, October 24, 2001, at 07:06 PM, cocoa-dev-
email@hidden wrote:

I have two libraries (.a) compiled from a makefile that I need to bundle up
into a framework. I've created a framework project in PB and have added the
headers and libraries. When I build the framework it doesn't contain any of
the symbols of the two static libraries.

How do I go about getting project builder to include these symbols in the
final framework?

--
Brian Webster
email@hidden
http://homepage.mac.com/bwebster


  • Prev by Date: Re: Is selector in protocol?
  • Next by Date: Re: Distributed Objects - Am I missing something?
  • Previous by thread: Wrapping conventional .a libraries in a framework...
  • Next by thread: Re: Wrapping conventional .a libraries in a framework...
  • Index(es):
    • Date
    • Thread