Yet Another Framework Linking bug.
Yet Another Framework Linking bug.
- Subject: Yet Another Framework Linking bug.
- From: Roy Lovejoy <email@hidden>
- Date: Mon, 24 Apr 2006 08:47:25 -0700
goodness.. all these issues that were not present in CodeWarrior, no
one has *any* answers for on XCode.
well, here's another hail-mary.
static lib Lib_A, with non-static routine Foo()
framework A includes Lib_A, but does not export Foo()
static lib Lib_B, also contains non-static routine Foo()
framework B includes, Lib_B, links to Framework A, does not export Foo()
of course, XCode complains that there are multiple definitions of
symbol _Foo, even though _no one_ is exporting it, and it's contained
within static libs.
is there a linker flag to tell XCode to ignore this?
dead stripping, suppressing multiple definitions, nothing seems to work.
_______________________________________________
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