Can't see carbon framework in second framework
Can't see carbon framework in second framework
- Subject: Can't see carbon framework in second framework
- From: Roy Lovejoy <email@hidden>
- Date: Fri, 21 Apr 2006 09:00:02 -0700
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