And please, don't say about Linux has interlibrary dependency for
shared libraries. First at all, not all libraries are shared
(even under Linux). Second, Linux is not only one flavor of Unix.
Linux is a kernel, the operating system you are refering to is called
GNU or in conjuction
pkg-config tries to solve an important problem, but it does so in the
wrong way. pkg-config checks for an exact library name,
PKG_CHECK_MODULES does not check for a library name at all,
but for the name of the .pc file. This gives the administrator
one extra level of
Alfred M. Szmidt wrote:
pkg-config tries to solve an important problem, but it does so in the
wrong way. pkg-config checks for an exact library name,
PKG_CHECK_MODULES does not check for a library name at all,
but for the name of the .pc file. This gives the administrator
On Fri, 23 Oct 2009, John Calcote wrote:
If your project uses libxml's API, then you as the maintainer should be very
aware of requisite dependencies of that library. The AC_CHECK_LIB macro
accepts a fifth argument, other-libraries, which is a whitespace-separated
list of dependent libraries
Bob Friesenhahn wrote:
In this case life would be better if all libraries had a .la file
and if Autoconf used libtool type functionality (e.g. consult the .la
files) as part of its testing.
Is there anything conceptually stopping us from writing a new
AC_LINK_IFELSE that links using libtool?
On Sat, 24 Oct 2009, Peter Johansson wrote:
Bob Friesenhahn wrote:
In this case life would be better if all libraries had a .la file and if
Autoconf used libtool type functionality (e.g. consult the .la files) as
part of its testing.
Is there anything conceptually stopping us from writing a
