From: Krzysztof Kosiński [mailto:tweenk.pl@...400...]
2010/5/26 Nicolas Dufour <nicoduf@...48...>:
> That's what I first thought, but no, not exactly. btool will stop if the
following files (from gettext-0.17-win32\bin) are not in the devlibs\bin
> After copying these file, I've been able to run btool successfully. Thus
I think it's the minimum requirement if we want to use the context C_()
macro. But we could also copy all the gettext-0.17-win32\bin content with
no risk, so that translators have all the needed tools without having to
I encountered that too. Right now I'm trying to build a version of
gettext 0.18 that links against intl.dll and iconv.dll from our
devlibs, so that the libraries are not duplicated. I also upgraded
Python to 2.6.5 and it appears to work correctly.
> My only doubt is about the gettext lib and include folders. Do we really
No, they are not needed, as we use the headers from gettext-runtime
that come in the official GTK+ Windows bundle.
I have tried to copy the files as mentioned, but I still get an error
Make error line 452: <msgfmt> problem: po/nl.po:18250: keyword "msgctxt"
po/nl.po:18250:8: parse error
po/nl.po:18255: keyword "msgctxt" unknown
po/nl.po:18255:8: parse error
po/nl.po:18260: keyword "msgctxt" unknown ...