[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Chosing between system and builtin library
From: |
Sylvain Beucler |
Subject: |
Re: Chosing between system and builtin library |
Date: |
Thu, 16 Oct 2008 08:40:59 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Oct 15, 2008 at 08:48:08PM +0200, Ralf Wildenhues wrote:
> Hi Sylvain,
>
> * Sylvain Beucler wrote on Tue, Oct 14, 2008 at 08:55:56PM CEST:
> >
> > (I'm not 100% sure this is the right list, please let me know if this
> > is the case :))
>
> Good enough, I'd say.
>
> > I'd like to implement something like gettext's inclusion of 'libintl',
> > which can be either included in the source tarball (for users), or
> > reused from a system library (for distros).
> >
> > gettext's implementation looks complicated. Is there an easier way to
> > do the job? I'm pretty sure there are some caveats to be aware of when
> > specifying the library.
>
> I think so. FWIW libltdl is similar (but probably even more
> complicated).
>
> Anyway, for a start I'd try to use an AC_CONFIG_SUBDIRS in the toplevel
> package (ignores non-existent subdirs), a subdir conigure for the
> library, and set LIBFOO, LTLIBFOO, INCFOO (or whatever naming)
> accordingly in a m4 macro that you ship to use. The important bit when
> using libtool is that you specify (and use) LTLIBFOO as sub/libfoo.la
> when internal. I think the gnulib module havelib can help you.
>
> Hope that helps.
Thanks, I'll have a look.
--
Sylvain