Quoting Eric Anholt (2018-01-17 12:58:27) > Dylan Baker <dy...@pnwbakers.com> writes: > > > Currently meson implements the same logic as SCons for translations, > > namely it doesn't do them. This patch changes meson to use logic more > > like autotools, and generate translations. To do this we have to go > > behind meson's back a bit, and wrap the whole thing up in a single > > python script. > > > > Meson has a module for gettext translations, but it assumes that one > > will have a pot file, and then .mo translations will be generated and > > checked into the source repo (or generated by hand using custom ninja > > targets before building), mesa assumes that the targets will be > > regenerated on each invocation of make or ninja. I think this can be > > fixed upstream, but in the mean time this adds support for using > > translations. > > Is there a reason you have a new python script, instead of having each > msgfmt invcation generating a mo file in its own custom target, and then > the custom target for the gen_xmlpool.py call depending on that?
Because generators and custom targets can't output into subfolders, so we can't use a meson level constructs to create the structure that gettext requires. I'd really like to just change the meson i18n stuff to be available at build time instead of creating run-targets, since that would do exactly what we want, but I haven't gotten there yet. I forgot to add that to the commit message.
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
