Am Montag 08 Juni 2009 22:32:43 schrieb Andreas Pakulat:
> On 08.06.09 22:12:00, Stefan Dröge wrote:
> > I solved my problem, and I think I've found a bug:
> > Since I'm German, my system language is set to German. Most programmes
> > have german console output, gcc too.
> > In CMakeFindEclipseCDT4.cmake the gcc output gets parsed, and
> > expecting a string "search starts here", but on my German system there
> > is only a "Suche beginnt hier" to find. ;-)
> >
> > My quick work around for this: set the language temporary to English like
> > this: export LANG=en_US.UTF-8
> > and then start cmake-gui, or cmake.
>
> Thats not really a bug, adding translation support for such compiler
> messages in code that tries to parse that output is insane (at least
> without the compiler offering a way to backtranslate its messages). In
> KDevelop3 we're having the same problem and there you have the choice of
> either getting nicely formatted (and shortened) compiler output or
> translated messages, but not both at the same time.
But if you start a child process to parse its output, you should always run it
in the default ("C") locale.
I you cannot do this for some reason: you can always choose the translation
domain with gettext and use the translated string to find the output.
HS
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
