Bug 45136 – [Qt] Make it possible to configure QtWebKit to use V8 (metabug)

• Status: RESOLVED
• Resolution: FIXED
• Component: New Bugs

[Vlad]

Make it possible to configure QtWebKit to use the V8 JavaScript engine instead of JavaScriptCore. At first, this would be useful for performance benchmarking and quality assurance.

[Simon Hausmann]

Changing the order of blocking/depends. The sub-tasks block this task. We can close this bug when the sub-bugs are fixed :)

[Simon Hausmann]

One idea for simplifying the build system changes a bit would be to replace the contains(QTJAVASCRIPTENGINE, V8) { ... } bits with a CONFIG, i.e. do

CONFIG += v8 at some point and then later on the test is a bit simpler:

v8 {
}

[Vlad]

Idealy js engine value should be passed here... something like

perl WebKitTools\Scripts\build-webkit --qt --symbian --v8

not sure if it translates into CONFIG... If yes, I agree it is simplest way. Another dependency for v8 is public header path...

(In reply to comment #2)
> One idea for simplifying the build system changes a bit would be to replace the contains(QTJAVASCRIPTENGINE, V8) { ... } bits with a CONFIG, i.e. do
> 
> CONFIG += v8 at some point and then later on the test is a bit simpler:
> 
> v8 {
> }

[Simon Hausmann]

WebKit trunk builds with V8 now, when --qt --v8 is passed to build-webkit and the Qt build is the one that contains the experimental port of QtScript to V8.

[Simon Hausmann]

This bug has a corresponding JIRA issue: <http://bugreports.qt.nokia.com/browse/QTBUG-13184>