[Top][All Lists]

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

Re: configuring libltdl

From: Bob Friesenhahn
Subject: Re: configuring libltdl
Date: Mon, 24 Nov 2003 10:35:34 -0600 (CST)

On Mon, 24 Nov 2003, Gary V. Vaughan wrote:

> Hash: SHA1
> Bob Friesenhahn wrote:
> | It seems to me that for packages which embed libtool and use libltdl,
> | it is very trivial for the package's configure script to also
> | configure libltdl.  This is *much* more efficient time-wise and
> | space-wise than a recursive configure.  The fact that the libtool
> | package uses a recursive configure sets a bad example that causes
> | libltdl to seem like a lot more overhead than it really needs to be.
> |
> | Should we convert the libltdl configuration to be part of libtool's
> | main configure script?
> Sure.  The libtoolize --ltdl and --ltdl-tar options will need to be reworked
> (what exactly is the point of ltdl-tar? Does anybody use it? And if so, why?).

There are a number of issues that would have to be handled in order to
properly integrate libltdl configure/build into the dependent
package's configure/build.  Historically, the libltdl directory has
been a fully-populated stand-alone directory.  All the dependent
package needs to do is include libltdl in SUBDIRS and then use the
library.  Of cource, this approach may double the size of small
packages, and double the time spent running configure.

Currently libltdl includes config.h like this:

#  include <config.h>

In order to use some configuration header name, or path, other than
<config.h>, the user needs to manually edit ltdl.c.  That is what I
have had to do with my packages.

It would be much better if there was a way to specify the package
configuration file name for ltdl.c to use.  For example

#if defined(LIBLTDL_CONFIG_H)
#  include <config.h>

Some means would need to be found for AC_LIB_LTDL to export the
package's configuration header name the same way that HAVE_CONFIG_H is
currently defined.  The definition would need to appear on the
compiler command line.

I am not sure what do to regarding the legacy expectation that the
files in the libltdl subdirectory are prepared like a full-fledged
stand-alone application.

The only files that would need to appear in the libltdl subdirectory
are COPYING.LIB, ltdl.h, ltdl.c,, and  There
is an issue with using since the user doesn't currently
need to use Automake in order to configure and use libltdl.

Bob Friesenhahn

reply via email to

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