Bug 33104
Summary: | [Qt] QtWebKit includes don't work if Qt was built with -no-script | ||
---|---|---|---|
Product: | WebKit | Reporter: | Bernhard Rosenkraenzer <bero> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | benjamin, kent.hansen |
Priority: | P1 | Keywords: | Qt |
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All |
Bernhard Rosenkraenzer
When using QtWebKit in a version of Qt that was configured with -no-script, the following error occurs:
In file included from /usr/local/Trolltech/QtEmbedded-4.7.0-arm/include/QtWebKit/QWebFrame:1,
from app.cpp:19:
/usr/local/Trolltech/QtEmbedded-4.7.0-arm/include/QtWebKit/qwebframe.h:28:36: error: QtScript/qscriptengine.h: No such file or directory
/usr/local/Trolltech/QtEmbedded-4.7.0-arm/include/QtWebKit/qwebframe.h:137: error: 'QScriptEngine' has not been declared
/usr/local/Trolltech/QtEmbedded-4.7.0-arm/include/QtWebKit/qwebframe.h:137: error: 'ValueOwnership' has not been declared
make: *** [app.o] Error 1
Probably just missing a couple of ifdefs...
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Benjamin Poulain
Effectively, some #ifdef are missing.
Kent Hansen
I guess the forwarding headers are not created.
We need to use the QScriptEngine::Ownership type, otherwise it won't be BC.
Can we use the relative path? That would be a patch specific to code living in Qt src/3rdparty/webkit, though. :-/
In the long term, if QtWebKit is going to link against QtScript and use the QtScript API for everything related to scripting, it seems like -no-script would actually imply -no-webkit.
Kent Hansen
*** This bug has been marked as a duplicate of bug 34519 ***