[Qt-interest] Reducing Qt footprint when using plugins

[Scott Aron Bloom]

Since Designer has to have the ability to display much of the GUI
library, I don't see any way you are going to be able to reduce the QT
footprint...

 

Scott

 

From: qt-interest-bounces at trolltech.com
[mailto:qt-interest-bounces at trolltech.com] On Behalf Of Christopher
Boger
Sent: Thursday, July 09, 2009 7:26 AM
To: qt-interest at trolltech.com
Subject: [Qt-interest] Reducing Qt footprint when using plugins

 

I am trying to reduce Qt's footprint for my embedded targets (linux and
CE). I've tried using the QConfig tool and alternatively simply removing
features with "-D QT_NO_<FEATURE>" method to prune out stuff I don't
use. This works pretty well for all the "standard" libraries (QtCore,
QtGui, QtNetwork, QtScript, QtXml). But, my app uses designer plugins so
I need to also build the QtDesigner library, which doesn't seem to play
nice with feature removal.

 

What I've discovered is that when using QConfig, it will by default
simply not build the tools, including the QtDesigner library. Using the
"-D QT_NO_<FEATURE>" will enable the QtDesigner build, but it's a
crapshoot as to whether QtDesigner needs that feature. Seeing as how
each iteration takes a long time (configure and build steps) and there
are a lot of features, I was hoping someone else has been down this path
and can tell me exactly what can be pruned out in QtDesigner.

 

Thanks!

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090709/64f6d2dc/attachment.html