Indirectly linked user dylibs
Indirectly linked user dylibs
- Subject: Indirectly linked user dylibs
- From: Glen Low <email@hidden>
- Date: Wed, 26 Nov 2003 18:15:14 +0800
Dear All,
Suppose I have an app that uses a dylib A, and that in turn uses a
dylib B, and the app and two dylibs are made by me (i.e. not system
dylibs). Suppose also (for now) that they are being built to the build
directory in my project directory with Xcode, and thus the correct
INSTALL_PATH for each dylib is @executable_path. And yes, I'm sticking
to two-level namespaces etc.
Questions:
1. For my executable, do I really have to link to both dylibs, since
dylib A already has a link to dylib B? Yet if I leave off dylib B, it
complains with:
ld: warning can't open dynamic library:
@executable_path/cdt.framework/Versions/A/cdt
during linking, which I can only silence by putting in the linker
option:
-dylib_file
@executable_path/cdt.framework/Versions/A/cdt:build/cdt.framework/
Versions/A/cdt
[Neither seems elegant to me, since I have to repeat the link chain,
but at least linking to 2 dylibs is visible in the Xcode GUI -- is
there some way to force the -dylib_file option from the GUI?]
2. What are the implications for loading performance / prebinding etc.
for the executable linked to both A and B, and for the executable just
linked to A alone?
Cheers, Glen Low
---
pixelglow software | simply brilliant stuff
www.pixelglow.com
_______________________________________________
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.