|
From: | Bob Friesenhahn |
Subject: | Re: MAC OS X, static compilation and libtool |
Date: | Tue, 18 Mar 2008 10:15:57 -0500 (CDT) |
On Tue, 18 Mar 2008, Peter O'Gorman wrote:
If linking libtool libraries, then libtool should add the full path to the static archive (e.g. ../foo/libfoo.a) when calling the linker. This will overcome even the OS X linker which searches all -L paths for a dylib before going back to the start again looking for a .a. Feel free to add -Wl,-search_paths_first to LDFLAGS if $host is darwin*. I am not sure that this should be handled in libtool, I'd be fine with adding it by default if another maintainer agrees.
I have always thought that libtool is doing the right thing. Most system linkers will choose a shared library over a static library unless special options or a full path is provided.
Is it possible that this reported problem could be due to a project issue? For example, is it possible that the libraries are being built in the wrong order so that the library is not available when it is needed to link the application? This would cause libtool to find the already installed library.
Bob ====================================== Bob Friesenhahn address@hidden, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
[Prev in Thread] | Current Thread | [Next in Thread] |