[Mesa-dev] [PATCH 4/5] util/gen_xmlpool: Add a --meson switch
dylan at pnwbakers.com
Fri Aug 24 18:45:56 UTC 2018
Quoting Emil Velikov (2018-08-24 08:57:29)
> On Fri, 24 Aug 2018 at 15:16, Dylan Baker <dylan at pnwbakers.com> wrote:
> > Meson won't put the .gmo files in the layout that python's
> > gettext.translation() expects, so we need to handle them differently,
> > this switch allows the script to load the files as meson lays them out
> No obvious reason comes to mind why we want divergence here.
> Can you elaborate more what's happening here - what are the .gmo
> files, I though we're using .mo ones?
Meson uses .gmo to distinguish that they are specifics GNU mo files, as opposed
to one of the other flaovrs like the solaris mo files, which use a completely
different syntax. The real difference is that autotools generates a folder
hierarchy to place the .mo (or .gmo) files in, but meson doesn't guarantee
folder structures in the build directory, so mimicking the autotools behavior
isn't guaranteed to work or continue working.
> If the only difference is a) extension and b) .mo file location - we
> could update the autoconf/others to follow the same pattern.
We certainly could change autotools to follow the same pattern if that's what
you wanted to do. I just don't have the expertise with autotools to do it
quickly, and I wanted to get something wired for meson.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 228 bytes
More information about the mesa-dev