[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib and static libraries
From: |
Bruno Haible |
Subject: |
Re: gnulib and static libraries |
Date: |
Fri, 9 Jul 2010 23:54:28 +0200 (MEST) |
Hi Simon,
> In this case, GnuTLS uses the read-file module from gnulib, and it ends
> up being exported in a static GnuTLS library. GNU Wget also has a
> function called read_file, and things break when linking.
> ...
> I have some vague memory that this has been discussed before (I may even
> have brought it up)
Yes, we discussed this topic in the thread started in
<http://lists.gnu.org/archive/html/bug-gnulib/2007-04/msg00232.html>.
I had been pointing you to gettext/gettext-tools/libgettextpo/Makefile.am;
nowadays the same technique is also used in libunistring/lib/Makefile.am.
In particular, look at this commit:
http://git.savannah.gnu.org/gitweb/?p=libunistring.git;a=commitdiff;h=d598f9e1e016735397e9dca53b436d13c6fb28f3
> Should `gnulib-tool --import' create AC_DEFINE's to map each global
> gnulib function symbol into some application provided namespace?
> E.g. `gnulib-tool --import --symbol-prefix _gnutls'? This would then
> create something like this:
>
> AC_DEFINE([read_file], [__gnutls_read_file])
>
> Maintaining the list of global gnulib functions will be a hassle
> though. Could this be automated?
Possibly. In the cases I needed, I did not have to hide all global symbols
coming from gnulib, but only some of them. I don't know whether in the
case you mention things get simple enough that gnulib could generate
the redirections in config.h.
Bruno