Re: AbiWord Windows builds and L10n workflow

Chris Leonard wrote on Mon, 25 Jun 2012 00:28:00 -0400:

> bafna_p ran into an issue while working on a Windows build.  He got a
> complaint that the

> /user/wp/strings/

> folder was missing.

Well, then. Fix the build.

> This apparently traces back to a modification of the MAKEFILE (or some
> such) made by Simon that causes the .strings files to be created on fly
> during the make.

Yes, we agreed on doing so after you asked "to automate the process without
requiring some cooperation from the developers as Pootle will only do the
commit of the PO file".

> This is great for *nix, but it does NOT address the needs of the Windows
> build process.

Why?

> As a temporary workaround to allow Windows build process  to move
> forward, I have re-generated all of the .strings using the PO files
> committed to SVN, by using the "abi-backport-all.sh" script to
> generate them and them moved them to /user/wp/strings/ and then
> committed that folder (and all the .strings files) to SVN.

Bad idea. We now have redundant data that soon will diverge. This ought to be
reverted ASAP.

> 2) What is the best approach ot solving this issue for the long term
> and addressing the needs of both *nix and Windows builders?

Fix the Windows build to generate the .strings files. Only Perl is needed for
the generation so it shouldn't be a problem.

> b)  Try to make a similar modification as that made for *nix makes
> that addresses Windows builds (in msvc?) so tha .strings files are
> created on the fly during the build.

Yes.

Ingo