Bug 33104 - [Qt] QtWebKit includes don't work if Qt was built with -no-script
Summary: [Qt] QtWebKit includes don't work if Qt was built with -no-script
Status: RESOLVED DUPLICATE of bug 34519
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P1 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-01-02 04:30 PST by Bernhard Rosenkraenzer
Modified: 2010-03-10 06:05 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Rosenkraenzer 2010-01-02 04:30:38 PST 
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...
Comment 1 Benjamin Poulain 2010-03-05 14:33:55 PST 
Effectively, some #ifdef are missing.
Comment 2 Kent Hansen 2010-03-10 05:59:34 PST 
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.
Comment 3 Kent Hansen 2010-03-10 06:05:15 PST 

*** This bug has been marked as a duplicate of bug 34519 ***