[Development] Can we bring back QT += declarative?

[martin.jones at nokia.com]

Reassigning "declarative" back to qtquick1 could be done.  I'm not sure that is an improvement since we have QtQuick 2 in the qtdeclarative module, so it actually becomes more confusing.

Martin.

> -----Original Message-----
> From: development-bounces+martin.jones=nokia.com at qt-project.org
> [mailto:development-bounces+martin.jones=nokia.com at qt-project.org]
> On Behalf Of Ramsay Lincoln (Nokia-MP/Brisbane)
> Sent: Friday, June 29, 2012 9:41 AM
> To: development at qt-project.org
> Subject: Re: [Development] Can we bring back QT += declarative?
> 
> On 06/29/2012 04:35 AM, ext Thiago Macieira wrote:
> > I'm trying to port a project to Qt 5 and the first thing I noticed
> > when I ran qmake is:
> >
> > Project ERROR: Unknown module(s) in QT: declarative
> 
> If you want QtQtuick1 that's now QT += quick1. This could probably use
> declarative now but previously that was used by QtQuick2.
> 
> In QtQuick2 there are 2 modules.
> 
> QT += qml gives you the engine (without a GUI dependency).
> QT += quick gives you the GUI-related classes.
> 
> Note that QDeclarativeXXX does not work with QtQuick 2 even after you
> update the QT variable so just allowing QT += declarative to enable
> QtQuick2 won't gain you anything.
> 
> --
> Lincoln Ramsay - Senior Software Engineer Qt Development Frameworks,
> Nokia - http://qt.nokia.com/
> 
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development