• 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: lazy type frame work linking question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lazy type frame work linking question


  • Subject: Re: lazy type frame work linking question
  • From: "Michael Crawford" <email@hidden>
  • Date: Mon, 16 Apr 2007 03:18:10 -0700

I don't know if GDB's linker dead-strips at the function level, but it
didn't used to: when the BeOS switched its compiler from MW CW to GDB,
I got a bunch of linking errors from functions that weren't
dead-stripped.

The solution is to put the code that needs the framework in a source
file all by itself.  I'm pretty sure the linker knows to remove unused
object files, but it may not be able to remove objects out of the
middle of an object file.

On 4/15/07, Tobias Ford <email@hidden> wrote:
 I'm looking
for the MW version of dead strip unused code.

I'll send you my bill in the mail. -- Michael David Crawford mdcrawford at gmail dot com

  Enjoy my art, photography, music and writing at
http://www.geometricvisions.com/
       --- Free Music Downloads ---
_______________________________________________
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


References: 
 >lazy type frame work linking question (From: Tobias Ford <email@hidden>)

  • Prev by Date: Re[2]: GDB crashing
  • Next by Date: A problem building shared library with -single_module and g++
  • Previous by thread: lazy type frame work linking question
  • Next by thread: A problem building shared library with -single_module and g++
  • Index(es):
    • Date
    • Thread