[webkit-qt] QtWebKit with reduced feature set for embedded platforms

steve.lewontin at nokia.com steve.lewontin at nokia.com
Thu Apr 8 05:10:27 PDT 2010

Just curious, what's the resource saving of QT_NO_ACTION turned on vs turned off?


From: webkit-qt-bounces at lists.webkit.org [webkit-qt-bounces at lists.webkit.org] On Behalf Of Hausmann Simon (Nokia-D-Qt/Oslo)
Sent: Thursday, April 08, 2010 4:45 AM
To: webkit-qt at lists.webkit.org
Cc: Suzuki Tasuku (Nokia-D-Qt/Tokyo)
Subject: [webkit-qt] QtWebKit with reduced feature set for embedded platforms


With Qt for embedded platforms we have the ability to disable various features
in Qt to reduce the library size. The features largely evolve around not
compiling certain classes, such as QMenu, QColorDialog or QAction, as well as
more general features such as QObject properties.

The features are controlled using defines, i.e. there's QT_NO_PROPERTIES,
QT_NO_CONTEXTMENU, QT_NO_PRINTER. We have a few of these in place the code.

Tasuku has been looking into compiling QtWebKit with less features enabled,
such as properties and QActions. See




Adding the feature #ifdefs adds a maintenance burden and clutters the code. On
the upside it makes it possible to use QtWebKit in much more restricted
environments, with limited functionality though.

What do you guys think about this? Do you feel this is a useful thing to have
and maintain?


More information about the webkit-qt mailing list