• 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
framework deadstrip?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

framework deadstrip?


  • Subject: framework deadstrip?
  • From: Roy Lovejoy <email@hidden>
  • Date: Tue, 25 Apr 2006 13:36:23 -0700

Perhaps this is the real problem I'm trying to solve.
(again, this is legacy code, being brought over from Codewarrior where it's smart enough to deal with this.
This is in no way shape or form best practice for new code)


In "Framework A" I have a routine:

static void Foo(void)
{
    extern void Bar(void);
    Bar();
}


__ and __

Foo() is not referenced by anyone
Bar() is not included/linked in "Framework A"

what linker setting(s) do I set so that XCode will *NOT* give me "missing symbol _Bar".
i.e. what setting will tell it to strip out Foo(), thus stripping out the Bar() dependancy.


-dead_strip doesn't work, and I don't want to use -undefined dynamic_lookup for fear of introducing a runtime error elsewhere.


_______________________________________________ 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: 
 >Yet Another Framework Linking bug. (From: Roy Lovejoy <email@hidden>)
 >Re: Yet Another Framework Linking bug. (From: "Peter O'Gorman" <email@hidden>)
 >Re: Yet Another Framework Linking bug. (From: Roy Lovejoy <email@hidden>)

  • Prev by Date: Interface Builder
  • Next by Date: Re: Interface Builder
  • Previous by thread: Re: Yet Another Framework Linking bug.
  • Next by thread: vpowf parameters backwards on Intel?
  • Index(es):
    • Date
    • Thread