Re: linking in private non-Framework libraries
Re: linking in private non-Framework libraries
- Subject: Re: linking in private non-Framework libraries
- From: Glenn Howes <email@hidden>
- Date: Mon, 30 Sep 2002 11:09:35 -0700
when I try to use the following command to configure my library build:
../dist/configure --exec_prefix @executable/../Resources
I get
error: expected an absolute path for --exec_prefix:
@executable/../Resources
Also, when I try --disable-shared on configure, the make fails.
On Monday, September 30, 2002, at 10:27 AM, Mike Davis wrote:
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.