Re: linking in private non-Framework libraries
Re: linking in private non-Framework libraries
- Subject: Re: linking in private non-Framework libraries
- From: Mike Davis <email@hidden>
- Date: Mon, 30 Sep 2002 18:27:11 +0100
I've not been following this thread, but dynamic libraries have a path
stored in them. This means that when it's compiled, it has to be loaded
*from* the path specified.
I tend to use a path relative to the executable, putting the dynamic
library inside the application wrapper, for example
"@executable/../Resources". I use a copy build phase to put the dylib
in the right folder.
Perhaps the make file you're using doesn't specify such a path?
M.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.