libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LT_* equivalent to AC_CHECK_LIB?


From: Sander Niemeijer
Subject: Re: LT_* equivalent to AC_CHECK_LIB?
Date: Tue, 4 Jul 2006 10:27:20 +0200

Here are some links to the archive that you might find interesting:

My suggestion for a LT_AC_CHECK_SHLIB:
http://lists.gnu.org/archive/html/libtool/2004-10/msg00222.html

Mind that there is a difference between linking a library against a library and linking a library against an application. When linking a library against a library you can not (portably) link a static library against a shared library. Since libtool is able to check for such things this was the reason that I wanted a special CHECK_SHLIB.

Links about LT_OUTPUT:
http://lists.gnu.org/archive/html/libtool/2004-11/threads.html#00372
http://lists.gnu.org/archive/html/libtool-patches/2005-08/msg00099.html

Best regards,
Sander

On 3-jul-2006, at 20:52, Tim Mooney wrote:


This seems like it should be an obvious question, but I'm not finding any
obvious answers in either the libtool or autoconf documentation.

Is there a libtool-aware equivalent to AC_CHECK_LIB? In other words, if I want to check for foo_amazing_func() in libfoo, and libfoo was built with libtool (and the libfoo.la is hopefully installed on the system), is there
an extant macro something like LT_CHECK_LIB(foo,foo_amazing_func) that
will try find foo_amazing_func() in libfoo *and* will pull in all the
necessary dependencies for libfoo, automatically?

The specific case I'm looking at is for a package that wants to check for libneon. Neon (which is a libtool library) might have been linked against OpenSSL (which might require pthread libraries and/or krb5 libraries), and
definitely requires one of libxml2 (which might have requirements like
zlib, pthread, libm, et. al.) or expat.  If I want to check for
libneon at configure time, using just AC_CHECK_LIB or AC_SEARCH_LIB will be extremely painful, because even with the fourth argument to either of
those macros, I'll still have to write a battery of configure tests to
figure out which particular combination of libraries is required to get
libneon and its dependencies.  If there's a libtool-aware equivalent
macro, it would be so much easier.

Tim
--
Tim Mooney address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164


_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool





reply via email to

[Prev in Thread] Current Thread [Next in Thread]