Re: static vs dylib lib linking
Re: static vs dylib lib linking
- Subject: Re: static vs dylib lib linking
- From: Hugh Hoover <email@hidden>
- Date: Fri, 23 Feb 2007 10:24:46 -0800
On Feb 22, 2007, at 12:50 PM, Dave Dribin wrote:
On Feb 22, 2007, at 12:59 PM, Kevin Packard wrote:
What is the correct way to specify linking with "libfoo.a" instead
of "libfoo.dylib" if both libraries reside in the same directory?
A way I've found that works well is to specify a the full path to
the .a as a custom linker flag. Basically, you want your linker
command line to look like this (notice no `-l` on the libfoo.a):
% ld -o output <object files> /full/path/to/libfoo.a -l<dynamic
library>
I've used this when I have a newer version of a system library that
I want to statically link against.
Another workaround is to remove or rename any dylib of the same name,
so you get -lfoo in the ld, but there is no libfoo.dylib, so it HAS
to link against the libfoo.a.
_______________________________________________
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