[webkit-qt] QtWebKit --minimal build with minimal Qt

Osztrogonac Csaba oszi at inf.u-szeged.hu
Tue Sep 27 06:52:03 PDT 2011


Hi QtWebKit developers,

The "Qt Linux Release minimal" buildbot on http://build.webkit.org is
our ifdef guard protector buildbot. It builds WebKit with this command:
Tools/Scripts/build-webkit --release --qt --minimal CONFIG+=qt_minimal
( details: http://build.webkit.org/buildslaves/szeged-linux-2 )

My question is if QtWebKit community still need supporting QT_NO_* guards in WebKit
trunk or not. If yes, which ones are still necessary and which ones can we drop?

br,
Ossy


Minimal Qt means that Qt was built the following QT_NO_* defines:
------------------------------------------------------------------
#define QT_NO_ANIMATION
#define QT_NO_BEARERMANAGEMENT
#define QT_NO_CLIPBOARD
#define QT_NO_COMBOBOX
#define QT_NO_CONCURRENT
#define QT_NO_CRASHHANDLER
#define QT_NO_CURSOR
#define QT_NO_DESKTOPSERVICES
#define QT_NO_FILEDIALOG
#define QT_NO_GRAPHICSEFFECT
#define QT_NO_IM
#define QT_NO_INPUTDIALOG
#define QT_NO_LINEEDIT
#define QT_NO_MESSAGEBOX
#define QT_NO_OPENSSL
#define QT_NO_PRINTER
#define QT_NO_QUUID_STRING
#define QT_NO_SHORTCUT
#define QT_NO_STYLE_STYLESHEET
#define QT_NO_SYSTEMTRAYICON
#define QT_NO_TEMPORARYFILE
#define QT_NO_TOOLTIP
#define QT_NO_UITOOLS
#define QT_NO_UNDOCOMMAND
#define QT_NO_UNDOSTACK
#define QT_NO_XRENDER

And the configure options:
---------------------------
-qconfig webkit-minimal
-platform linux-g++-32
-embedded
-nomake demos
-nomake docs
-nomake examples
-no-webkit
-no-openssl
-no-declarative
-no-scripttools
-opensource


More information about the webkit-qt mailing list