This bug report originated from issue QTBUG-7339 http://bugreports.qt.nokia.com/browse/QTBUG-7339 --- Description --- I built Qt 4.6 statically on a Ubuntu 9.10 box using the following flags: <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">/path/to/src/configure -prefix /usr/local/Trolltech/Qt-4.6.0-<span class="code-keyword">static</span> -release -opensource -<span class="code-keyword">static</span> -fast -qt-sql-sqlite -no-qt3support -nomake <span class="code-quote">"demos examples"</span> -silent -platform linux-g++-32</pre> </div></div> <p>Which builds just fine. When I try to compile one of my applications (which have a <tt>QT += webkit</tt> line), I get the following error:</p> <p><tt>/usr/local/Trolltech/Qt-4.6.0-static/include/QtWebKit/QtWebKit:15:32: error: qwebplugindatabase.h: No such file or directory</tt></p> <p>After some exploring I found out that the above file includes <tt>qwebplugindatabase.h</tt> even on static builds. Since plugins are not supported on static builds, this line shouldn't be there.</p> <p><b>Workaround:</b><br/> A quick workaround is to use more granular includes, like <tt>#include <QtWebKit/QWebFrame></tt> instead of <tt>#include <QtWebKit></tt>.</p>
This seems like another Qt specific (as opposed to QtWebKit specific) build problem.
We now to the module header and class headers as part of the WebKit/qt/Api derived sources, so the fix for this should be made in trunk.
The QtWebKit module header should include all header files, and the headers should be usable regardless of the build configuration. Is this an issue in trunk still?
Actually we don't really support static builds, so closing this for now, unless the original reporter (not me) reopens it with a valid test-case for trunk.