Qt-interest Archive, January 2007
How to remove support for Qt3.x ???
Message 1 in thread
Hi,
How can I remove support, to my build, for Qt-3.x ?
Cheers,
Joshua
--
[ signature omitted ]
Message 2 in thread
Hi Joshua,
you only have a dependency to the Qt 3 support library when you link
against it.
Nevertheless, you can configure Qt with "configure -no-qt3support". When
you then rebuild Qt the Qt 3 support libs are not created anymore.
Regards,
Falko
--
[ signature omitted ]
Message 3 in thread
> you only have a dependency to the Qt 3 support library when you link
> against it.
> Nevertheless, you can configure Qt with "configure -no-qt3support". When
> you then rebuild Qt the Qt 3 support libs are not created anymore.
Iirc, you can write code that works w/o a dependency to Qt3Support (I mean
the shared lib), but does not work (or maybe even compile) if your Qt is
configured without with -no-qt3support.
I.e. if you really want to be sure not to use Qt3 stuff then it is a good
idea to compile Qt without support for Qt3.
One thing I remember is that some signal connections have changed - the
default for QAction is triggered now, and something else (activated?) used
to work in Qt3. This issue popped up only when compiling without Qt3
support - although I thought I was 'clean'.
If my memory should be wrong, sorry. Just a warning.
--
[ signature omitted ]
Message 4 in thread
"Christoph Duelli" <duelli@xxxxxxxxxxxx> wrote in message
news:entuf7$82u$1@xxxxxxxxxxxxxxxxxxxxx
> > you only have a dependency to the Qt 3 support library when you link
> > against it.
> > Nevertheless, you can configure Qt with "configure -no-qt3support". When
> > you then rebuild Qt the Qt 3 support libs are not created anymore.
> Iirc, you can write code that works w/o a dependency to Qt3Support (I mean
> the shared lib), but does not work (or maybe even compile) if your Qt is
> configured without with -no-qt3support.
> I.e. if you really want to be sure not to use Qt3 stuff then it is a good
> idea to compile Qt without support for Qt3.
>
> One thing I remember is that some signal connections have changed - the
> default for QAction is triggered now, and something else (activated?) used
> to work in Qt3. This issue popped up only when compiling without Qt3
> support - although I thought I was 'clean'.
>
> If my memory should be wrong, sorry. Just a warning.
Qt3 support does seem to change some function calls etc. but you
enable this by a define in your project. You then have to link the lib.
It's not just having the support lib built in Qt.
Configuring without support libs would be useful though if you don't
use them as the compile can be long. We've just been using the
Windows binaries out of the box though so we don't usually need to
do configure/make.
--
[ signature omitted ]
