"Thiago A. Corrêa"
thiagoacorrea at uol.com.br
Fri Jan 7 19:32:58 CET 2005
Christian Ehrlicher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Chris January schrieb:
> |>Chris January schrieb:
> |>| Can someone more familiar with qmake than me fix it so that
> |>applications are
> |>| linked against qt-mt333.lib instead of qt-mt.lib? Or
> |>perhaps it is my
> |>| mistake?
> |>What's the problem linking against qt-mt333.lib? Where do you
> |>get qt-mt.lib from? When I link qt-mt333.dll, qt-mt333.lib is created.
> | When I compile Qt/Win Free using MSVC.NET it generates qt-mt333.lib and
> | qt-mt333.dll. If I think run qmake on psi (the open-source jabber
> | it will generate Makefiles that attempt to link against qt-mt.lib
> I've found no option for (i)link to create a libname other than the
> dll-name. So my only idea is to create qt-mt.dll or change qmake.conf.
> But since qmake.conf shouldn't be edited...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> kde-cygwin mailing list
> kde-cygwin at kde.org
I noticed that once while porting Qt for wolfpack.
Check your .qmake.cache for QT_VERSION_OVERWRITE
More information about the kde-cygwin