multiple configure.ac's in a project?

[Simon Josefsson]

Hi,

In GnuTLS I'm using several configure.ac:

configure.ac
lib/configure.ac
libextra/configure.ac

The reason for this was that gnulib worked better with this setup, but
there are other arguments as well (although, alas, not autoreconf
speed!).

However, this complicates the gettext setup.  There is one "gnutls"
gettext domain.

The options appears to be:

1) Use one gettext domain per configure.ac.

   In other words, there will be:

   "gnutls" in po/ for command line tools
   "libgnutls" in lib/po for libgnutls messages
   "libgnutls-extra" in libextra/po for libgnutls-extra messages

  Is this what you would recommend?

  I would have to ask the translation team to rename the current
  "gnutls" domain into "libgnutls" since currently only messages from
  the library is in the "gnutls" domain.

  This approach appears sub-optimal to me, but maybe you have more
  insight to this.

2) Use one "gnutls" gettext domain for the entire project, putting the
   translation files in the top-level po/.

   This leads to problems in the code in lib/ and libextra/: ENABLE_NLS
   is not set, so the gettext function is null.

   If I add AM_GNU_GETTEXT to lib{,extra}/configure.ac it will require
   that directories lib/po/ and libextra/po/ exists -- since the macro
   and the autopoint tool requires that.

   Further, I couldn't seem to get it to generate lib/po/Makefile and
   libextra/po/Makefile, it seems as if the autoconf rule to work in a
   po/ directory was satisfied after creating the top-level po/Makefile.

   How should code in lib/ and libextra/ use the gettext function?

Thanks,
/Simon