|
From: | Andrew Smith |
Subject: | Re: Whys is `make dist` packaging gmo files? |
Date: | Thu, 09 Aug 2007 08:38:07 -0400 |
User-agent: | Thunderbird 2.0.0.5 (X11/20070716) |
Eric Blake a écrit :
Oh, well I guess if they're portable it doesn't matter. I freaked out a little when I realised that running ./configure && make in a newly extracted dist tarball doesn't recompile the po files.According to Andrew Smith on 8/9/2007 12:34 AM:They compile and install and run fine. But when I do `make dist` I end up with sv.gmo and zh_TW.gmo (as well as the expected sv.po, zh_TW.po) in my po dir. I thought these were binary and not portable?They are indeed binary, but they ARE portable, as the file layout is specifically machine-independent. Read up on .gmo files in the gettext manual. When you install an internationalized package, it is the .gmo file that gets placed into the locale directory (renamed to .mo); the gettext() function is more efficient operating on a binary file than it would be on the source .po that generated it.
Yeah I meant avoid packaging them in the release tarball, I know they have to be compiled before they're usable.Would someone share why this may be happening and what I can do to avoid it?You don't want to avoid it, otherwise your package would not have i18n support.
Also I just noticed a make clean doesn't delete the .gmo files.How about 'make distclean'?
Nope, still there. I have autoconf 2.61. Thanks Eric Andrew
[Prev in Thread] | Current Thread | [Next in Thread] |