Enrico Forestieri wrote:
Michael Gerz <[EMAIL PROTECTED]> writes:
Enrico Forestieri wrote:
Then why not compiling libiconv with mingw, too? It is quite strightforward
to do. As regards gettext, if you configure with --with-included-gettext,
it will be compiled alongside LyX.
Then why not keeping the option? Why all the trouble?
I am neither against nor pro it. I have tried compiling LyX with and
without it, and it seems to make no difference for me. However, Abdel
found that it hurts him. Given that it is simpler adding it to CPPFLAGS
if it is needed than getting rid of it if it hurts, I think that the most
logical thing to do is not enforcing it. I am fine with whatever resolution.
Enrico,
Using MSYS, I have built the libiconv package suggested by Michael and then
gone on to build LyX using --with-included-gettext. configure finds
libiconv and the build proceeds happily, but I find that the resulting .exe
is unable to change the installed .po (.gmo) dynamically to the local
locale. If I understood your message of some time ago correctly, you
reported that your essentially-identical cygwin build was able to display a
Polish LyX with native Windows LANG.
When I read the libiconv/gettext build docs, it seems that the build
process is essentially circular. First build gettext, then libiconv, then
gettext again. (Or start with libiconv, then gettext, then libiconv again.)
So, I suspect that my build doesn't work as advertised because my build is
incomplete.
Before I invest time and effort into trying out my theory, can you explain
in more detail just what you did to get this stuff working?
Regards,
Angus
