Jonas Fonseca <[EMAIL PROTECTED]> writes: > However, after running cg-export we run ./autogen.sh, > ./configure and for the HEAD branch 'make -C po' so that people without > the autotools and gettext tools installed can use the tarballs.
I am surprised you tar up an already configured tree, as INSTALL tells the user to run ./configure. >> Anyway, po/*.gmo wouldn't be the only generated files in the >> source tree. Specifically, autogen.sh places several files >> there: acinclude.m4, aclocal.m4, config.h.in, and configure. >> If storing po/*.gmo in the source tree would cause you trouble, >> how do you cope with these? > > They are kind of different, IMO, since those generated files can be > shared across several builds, no? po/*.gmo can also be shared across builds, if po/*.po are the same in each build. If the po/*.gmo files depended on the user's compilation environment or configuration options, there'd be no point in adding them in elinks-*.tar.gz. (IIRC, there are big-endian and little-endian variants of the GNU MO format, but the GNU Gettext library can recognize and convert them on the fly.) If the user is building ELinks with a gettext library and a msgfmt program that don't use the same file format as GNU Gettext does, then the files should indeed be placed in the build directory. In that case however, they should called po/*.mo rather than po/*.gmo.
pgpSCK4CnbZnV.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
