those installation directories again
those installation directories again
- Subject: those installation directories again
- From: Stefan Werner <email@hidden>
- Date: Tue, 31 Jan 2006 16:34:48 +0100
Hi,
I'm really having a hard time with the installation directories that
get encoded in dylibs. The situation is the following:
I have a shared build directory, in which I want to build application
A.app. A.app depends on X.dylib, which again depends on Y.dylib.
X.dylib is supposed to be put inside the application bundle, why its
installation directory is set to @executable_path/../Frameworks.
Y.dylib is also supposed to go there, so I set the same installation
directory. However, then the linker doesn't find Y.dylib while
linking X.dylib, because it's looking in @executable_path/../
Frameworks relative to build product X.dylib. How do I resolve this?
What installation directory do I set for Y? When I leave it blank,
Xcode appears to use the absolute path to the library in my build
products directory, which is not what I want it to be. Is there
anyway to tell the linker to explicitly link against Y.dylib and to
ignore the path that's encoded in the file?
Thanks,
Stefan
_______________________________________________
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