Yeah well, if you made a static Qt build, and link to qjpeg.lib, you
also need to link to the static versions of all the Qt libs (i.e.
> -----Original Message-----
> From: Kirby Frugia [mailto:hpkirby@xxxxxxxxx]
> Sent: Monday, June 25, 2007 8:18 PM
> To: Peter Prade
> Cc: qt-interest@xxxxxxxxxxxxx
> Subject: Re: Link imageformat plugins statically
> I should say, in both cases I'm linking to the shared Qt libs (core,
> On 6/25/07, Kirby Frugia <hpkirby@xxxxxxxxx> wrote:
> > Thanks for the response.
> > We would like to keep Qt linked statically so we can share Qt with
> > other applications of ours.
> > It's qjpeg1.lib if you build Qt shared. If you build it statically,
> > it's qjpeg.lib. I've tried both, but get link errors in both cases.
> > When I link to the non-static plugin, I get the following link
> > main.obj : error LNK2019: unresolved external symbol "class QObject
> > __cdecl qt_plugin_instance_qjpeg(void)"
> > (?qt_plugin_instance_qjpeg@@YAPAVQObject@@XZ) referenced in function
> > "public: __thiscall
> > StaticqjpegPluginInstance::StaticqjpegPluginInstance(void)"
> > (??0StaticqjpegPluginInstance@@QAE@XZ)
> > C:\workspace\head\hurricane-sw-
> > : fatal error LNK1120: 1 unresolved externals
> > When I link to the static plugin, I get the following link errors:
> > qjpeg.lib(main.obj) : error LNK2005: "public: __thiscall
> > QString::QString(class QString const &)" (??0QString@@QAE@ABV0@@Z)
> > already defined in QtCore4.lib(QtCore4.dll)
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/