On 4/14/05, D.J. Heap <dj@shadyvale.net> wrote:
> Ben Collins-Sussman wrote:
> [snip]
> >
> > We've built a 1.2.0-rc1 .zip, but
> >
> > * we have no .mo files. build_locale.bat isn't being run for some
> > reason...? The only difference between our .zip and Branko's is that he
> > includes share/locale/*.
> [snip]
>
> It looks like if you have the --enable-nls option (you do) then the .mo
> files are created in the same directory as the .po files which is
> subversion\po rather than somewhere in release\subversion.
Yes, we do. We use --enable-nls as well as -with-libintl which is
documented to imply --enable-nls. I've tried all three possible
combinations of passing them to the gen_make command.
>Are they not
> even in subversion\po? The build_locale.bat file should be running
> python and msgfmt for each po file after gen_make.py has created
> it...does it have anything in it?
No. In none of the three cases.
> They are being created for me when I build. I'm not sure why they
> aren't going into the release or debug directory...perhaps the
> build_locale.ezt just needs to be tweaked to put them there. I'll try
> to look at it this weekend, if that is something we want?
Yes, we definitely want everything which should go into a release in
Release\ . Also, that makes it predictable where to look for output.
Which commandline options do you use for gen_make?
> DJ
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 14 08:24:34 2005