[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE/kdepim/kleopatra
From:       David Faure <dfaure () kdab ! net>
Date:       2008-06-19 9:16:02
Message-ID: 200806191116.04601.dfaure () kdab ! net
[Download RAW message or body]

On Wednesday 18 June 2008, Dirk Mueller wrote:
> On Tuesday 13 May 2008, Jaroslaw Staniek wrote:
> 
> > no idea why that suddenly become a must for Qt 4.4: redef QT_NO_STL and
> > QT_STL
> >
> >
> >  M  +6 -0      crypto/gui/resolverecipientspage.cpp
> >  M  +6 -0      uiserver/echocommand.cpp
> >
> >
> > --- trunk/KDE/kdepim/kleopatra/crypto/gui/resolverecipientspage.cpp
> > #807410:807411 @@ -32,6 +32,12 @@
> >
> >  #include <config-kleopatra.h>
> >
> > +#ifdef QT_NO_STL
> > +#undef QT_NO_STL
> > +#undef QT_STL
> > +#define QT_STL
> > +#endif
> 
> That sounds wrong, it is a qfeature check. 

It is, but it only changes typedefs and stuff in header files, no changes to the compiled code for Qt,
so enabling it afterwards works too, even though it's ugly.

> do you build qt4 without STL  
> support? has anyone else have an issue with that? is this a non-Unix platform 
> issue?

Yes, by default Qt is built on Windows without RTTI, STL, or exceptions, iirc.

-- 
David Faure, faure@kde.org, dfaure@kdab.net
KDE/KOffice developer, Qt consultancy projects
Klarälvdalens Datakonsult AB, Platform-independent software solutions

[prev in list] [next in list] [prev in thread] [next in thread]