[Qt-interest] Fwd: Can I build Qt with built-in jpeg support ?

[liang jian]

    to Mark Brand : I get Qt source code from git repository (4.7
branch). I have read the comment, and it seems that I have to wait.
thank for your reply!

    to Konstantin Tokarev : the reason why I care about a built-in
jpeg support is that there is memory leak in factory loader (please
refer to http://bugreports.qt.nokia.com/browse/QTBUG-4341), If I use
jpeg image format through a plugin, there will be memory leaks report
during application exiting and I can't tell the leak caused by myself
from the leak caused by Qt plugin.

On Tue, Feb 15, 2011 at 1:09 AM, Mark Brand <mabrand at mabrand.nl> wrote:
>
>>> At 2011-02-14，"liang jian"<jianliang79 at gmail.com>  wrote:
>>>>
>>>>     I mean Is it possible for me to build a Qt library (shared, not
>>>> static, and I build under windows) with jpeg image format support but
>>>> without a jpeg plugin ? I know png is built into qt library by
>>>> default, how can I build jpeg in that way?
>
> On 02/14/2011 04:36 PM, liang jian wrote:
>>
>>    hi, achellies, even when I configure qt with the "-qt-libjpeg"
>> option it will build jpeg into a plugin.
>>    but I found a clue: there is a line in %QTDIR%\src\gui\image\image.pri
>> :
>>    contains(QT_CONFIG, jpeg):include($$PWD/jpeghandler.pri)
>>    I guess if jpeg is defined in QT_CONFIG, jpeg will be build
>> directly into qt library. I also found that QT_CONFIG is defined in
>> %QTDIR%\mkspecs\qconfig.pri and jpeg is not defined in this file (but
>> png is defined). qconfig.pri is a file generated by configure.exe, the
>> question is how can I affect QT_CONFIG by the command options passed
>> to configure.exe, I currently have no idea, can somebody help? thanks
>>
>
> You didn't mention which Qt version you are using.
>
> Before Qt 4.7.1 the image format handlers are plugins.
>
> Since Qt 4.7.1 the image format handlers can be built-in or plugin. The
> comment explains it here:
>
> http://qt.gitorious.org/qt/qt/commit/802dc404d1af9a08fdc23ef32e2fbc77f138f70a
>
> Summary: Plugin-in for shared. Built-in for static.
>
> There is still no configure switch to override the default, although I
> noticed that this has been added to the master branch.
>
> regards,
>
> Mark
>