45136 2010-09-02 15:23:41 -0700 [Qt] Make it possible to configure QtWebKit to use V8 (metabug) 2011-02-23 07:40:15 -0800 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) All All RESOLVED FIXED P3 Normal --- 45140 45141 45142 45144 45145 45146 45147 45148 45149 45150 45157 1 vladbph vladbph abarth abecsi christian.webkit cmarcelo eostroukhov hausmann henry.haverinen japhet kbalazs kent.hansen kling laszlo.gombos loki luiz ossy pvarga s.mathur tonikitoo webkit-ews yael zherczeg oldest_to_newest 273612 0 vladbph 2010-09-02 15:23:41 -0700 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. 273808 1 hausmann 2010-09-02 23:52:13 -0700 Changing the order of blocking/depends. The sub-tasks block this task. We can close this bug when the sub-bugs are fixed :) 273930 2 hausmann 2010-09-03 07:20:21 -0700 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 { } 274008 3 vladbph 2010-09-03 10:12:00 -0700 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 { > } 281475 4 hausmann 2010-09-20 02:50:00 -0700 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. 281476 5 hausmann 2010-09-20 02:50:26 -0700 This bug has a corresponding JIRA issue: <http://bugreports.qt.nokia.com/browse/QTBUG-13184>