Quoting Emil Velikov (2018-08-24 08:57:29) > On Fri, 24 Aug 2018 at 15:16, Dylan Baker <dy...@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. Dylan
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
