Re: Yet Another Framework Linking bug.
Re: Yet Another Framework Linking bug.
- Subject: Re: Yet Another Framework Linking bug.
- From: "Peter O'Gorman" <email@hidden>
- Date: Tue, 25 Apr 2006 00:56:15 +0900
On Mon, 2006-04-24 at 08:47 -0700, Roy Lovejoy wrote:
> 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.
Either create and export symbol list for your frameworks and ensure that
Foo is not listed there, or make Foo a private_extern function in the
static library (hint use nmedit or gcc's visibility attrtibute).
<http://developer.apple.com/documentation/developertools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html>
Peter
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________
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