|
|
> >*RE-LINKING* You don't have to re-link when you upgrade your Qt library,
> > as long as the version is >= 3.2 and <= 3.9.
>
> As long as the qt library on windows contains the full version number
> (qt-mt334.dll), you always have to relink on windows.
:) Just re-name e.g. qt-mt335.dll to qt-mt334.dll. Could hardly be any harder
than that. Those numbers don't mean much anyway and I have always ignored
them. I have gizmos like qt-mt320.dll that are really the latest Qt. I mean,
who cares?
> I think, the
> library name should be qt-mt3.dll
Or rather qt-mt3-2.dll, indicating that it's the second ABI release for qt3.
> I think they don't support it, because qt runs on a large number of
> platforms and exporting symbols from a statically linked executable may
> not be possible for all supported platform/compiler combinations. If you
> use g++ on IRIX for example, you can't use the -exported_symbol flag of
> the linker, because g++ silently adds the -hidden_symbol flag when
> linking and the linker allows only one of the flags to be specified.
That will change with gcc4 IIRC. For now, it should be easy enough to get rid
of it in the specs file (i.e. w/o recompiling gcc).
Cheers, Kuba
--
List archive and information: http://lists.trolltech.com/qt-interest/
|
|