Qmake problem

[Chris January]

> On Saturday 08 January 2005 14:48, Christian Ehrlicher wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > | As far as i know, does mkspecs/qmake.conf defines two 
> variables for
> >
> > using the
> >
> > | qt library in other projects/apps, which indicates that 
> the release
> >
> > number
> >
> > | has not be included into the import lib.
> > |
> > | QMAKE_LIBS_QT  = qt.lib
> > | QMAKE_LIBS_QT_THREAD = qt-mt.lib
> >
> > No, these two variables are expanded with the 
> version-number. For an 
> > example see msvc_nmake.cpp lines 585-595.
> >
> perhaps somebody can try to check if qt installs the libs in 
> the same manner 
> as under linux, there you have the real library, and a set of 
> links pointing 
> to it:
> 
> lrwxrwxrwx  1 root root      13 Sep  9 01:11 libqt-mt.so -> 
> libqt-mt.so.3
> lrwxrwxrwx  1 root root      15 Sep  9 01:11 libqt-mt.so.3 -> 
> libqt-mt.so.3.3
> lrwxrwxrwx  1 root root      17 Sep  9 01:11 libqt-mt.so.3.3 -> 
> libqt-mt.so.3.3.3
> -rw-r--r--  1 root root 7239720 Sep  9 01:11 libqt-mt.so.3.3.3
> 
> 
> perhaps it is possible to make some similar links under 
> windows. so programs, 
> that need qt 3 can link to say qt-mt-3.lib, and others, that 
> need at least 
> qt-mt-3.3.lib...
> 
> just my 2c, i am not that familiar with windows at all...

This isn't really possible under Windows - it doesn't support symlinks
(junctions) for files.

Chris