[Qt-interest] libiconv is used on Windows after all?

Nikos Chantziaras realnc at arcor.de
Tue Jun 21 15:19:11 CEST 2011


Yes, it's a static Qt build.  However, there are no link errors if I 
build static but with libiconv.  Only without it does the linker bark, 
which looks weird to me.


On 06/21/2011 03:05 PM, Constantin Makshin wrote:
> No, it's really not necessary.
>
> These functions look like they're from text codec plugins. May be you're trying to build an application using static version of Qt and forgot to properly configure/link used plugins?
>
> On Tuesday, June 21, 2011 09:59:16 AM Nikos Chantziaras wrote:
>> According to a comment by Thiago:
>>
>> http://lists.qt.nokia.com/pipermail/qt-interest/2010-August/026692.html
>>
>> "libiconv is not used on Windows."  So I tried building Qt without
>> libiconv.  It builds fine.  However, trying to build a Qt application
>> results in:
>>
>>     undefined reference to `QGb18030Codec::QGb18030Codec()'
>>     undefined reference to `QGbkCodec::QGbkCodec()'
>>     undefined reference to `QGb2312Codec::QGb2312Codec()'
>>     undefined reference to `QEucJpCodec::QEucJpCodec()'
>>     [and many more]
>>
>> So I suppose for QTextCodec to work, libiconv is needed after all?




More information about the Qt-interest-old mailing list