Re: Yet Another Framework Linking bug.
Re: Yet Another Framework Linking bug.
- Subject: Re: Yet Another Framework Linking bug.
- From: Roy Lovejoy <email@hidden>
- Date: Mon, 24 Apr 2006 12:57:38 -0700
On Apr 24, 2006, at 8:56 AM, Peter O'Gorman wrote:
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).
Thanks for replying, but as stated in the problem,
Foo() is not being exported, e.g. it's NOT in the export symbol list.
In both frameworks, I have explicit export files NOT containing the
symbol in question,
yet XCode says there's a collision.
another quite odd thing XCode is doing to me is that, due to massive
editing over many years, this one source file wound up to have a
_single_solitary_ static routine that was, metaphorically:
static void Foo()
{
Bar()
}
only routine in the file.. (impossible to reference externally)
and yup, XCode complained that Bar() was undefined at link time.
Codewarrior simply had said "Foo() isn't used by anyone, ergo Bar()
missing is inconsequential"
for what it's worth, I usually only post on mailing lists when
a) I'm doing the right thing
b) man pages fail to deliver an explanation/work around
c) Apple's ADC website fails to deliver an explanation/work around
d) Google search fails to provide explanation/workaround
that is the situation with these link problems i've posted on this list.
_______________________________________________
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