Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2001:
[Freeciv-Dev] Re: cvs compiling problem (PR#1128)
Home

[Freeciv-Dev] Re: cvs compiling problem (PR#1128)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Cc: freeciv-dev@xxxxxxxxxxx, Thue Janus Kristensen <thue@xxxxxxx>
Subject: [Freeciv-Dev] Re: cvs compiling problem (PR#1128)
From: Jason Short <vze2zq63@xxxxxxxxxxx>
Date: Mon, 17 Dec 2001 16:20:58 -0500
Reply-to: jdorje@xxxxxxxxxxxx

Per I. Mathisen wrote:

On Mon, 17 Dec 2001, Ben Webb wrote:

        msgfmt is needed to build the .gmo files from .po files; gettext
in intl/ uses these .gmo files to localize the code. So, on systems
_without_ gettext, you need to provide the gettext code in intl/ and the
.gmo files. This is fine for a "stable" distribution, which should include
the .gmo files (try a "make distclean" in po/ - it doesn't delete the
.gmo files) but awkward for CVS, since the .gmo files aren't text. So the
solution is to not include the .gmo files in CVS, and require the user to
have the msgfmt tool if they want to play with dodgy unstable code.


Ah, of course. The best solution is to compile and include the .gmo files
in the stable source releases. I suppose make would not create an error
then, but I am not sure. However, there should still be a clear test in
configure for this, for those who get source from cvs or cvs snapshots.

Sounds like the .gmo's are already included in the stable release, or any tarball for that matter. Try "make dist" to see.

Checking for msgfmt will be tricky, since the check should only occur if we're compiling from CVS. That is, we must either have the .gmo's (up-to-date) _or_ have msgfmt. In a different project this might go in an autogen.sh file, but freeciv does not use such a system.

jason




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