Weak linking 3rd-party frameworks
Weak linking 3rd-party frameworks
- Subject: Weak linking 3rd-party frameworks
- From: Laurence Flath <email@hidden>
- Date: Wed, 25 Aug 2004 13:40:46 -0700
I searched the archives for weak-linking, but it's almost all on OS
compatibility; please inform me if I missed it!
Using 10.3.5, Xcode 1.5.
I have a framework target that I'd like to embed in my apps so my
in-house users can DnD them without an installer (using the
@executable/../Frameworks install path). My framework and the
executable(s) are in different project files.
My custom framework links to a third-party framework (installed in
/Library/Frameworks) which is rarely used, but nonetheless necessary
for certain applications. I have no control over how that library was
built. The -weak_framework linker flag seems like the answer, but it
isn't working for me.
The application builds and runs fine on my development machine, but
when I bring it over to a clean system, it launches and immediately
quits. Console logs a dyld error, saying it can't find the third-party
framework in /Library/Frameworks.
I'm guessing the solution is some combination of target switches on
either or both of my projects, but there are quite a few
combinations...
Thanks for any help!
Laurence
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.