Re: Can't see carbon framework in second framework
Re: Can't see carbon framework in second framework
- Subject: Re: Can't see carbon framework in second framework
- From: "William H. Schultz" <email@hidden>
- Date: Fri, 21 Apr 2006 10:40:08 -0700
Can't say for certain if this will help, but I figured I'd look
through my stuff, since I'm doing some similar stuff without any
problems...
On my equivalent of Framework A, I have things like '-undefined
error' and '-twolevel_namespace_hints.'
On my equivalent of Framework B, I also have '-nomultidefs.' If you
know that symbols will be available at runtime, you could also use '-
undefined dynamic_lookup.' (e.g. for inter-dependent plugins.)
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/
On Apr 21, 2006, at 9:00 AM, Roy Lovejoy wrote:
I'm hoping someone can perhaps answer *this* simple XCode linking
question.
In a single project, I have Framework A that links to Carbon, and
Framework B that links to Framework A, and to Carbon.
Framework A builds just fine.. no link errors.
Framework B has hundreds of link errors, of the nature:
../Framework_A(single module) reference to undefined _GetDialogPort
expected to be defined in Carbon
framework access paths are identical, 'reveal in finder' shows they
are linking to the same physical Carbon framework.
everything can 'see' everything else..
this is insanely frustrating.
if I remove Carbon as being a target in Framework A, it doesn't
link because it still needs Carbon.
if I remove Carbon as being a target in Framework B, I don't get
the "expected to be defined" link errors.. only the link errors
because Framework B _NEEDS_ the routines defined in Carbon too.
it's gotta be some arcane linker flag, but I can't see which.
_______________________________________________
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