Qt WebEngine Technology Preview Available - Qt BlogStatus QtWebEngine in KDEPIM
As QtWebKit will be remove from official Qt package I decided some months ago to evaluate QtWebEngine.
For sure QtWebEngine & 5.6 was too limited. But I started to use it. I evaluated QtWebEngine 5.5 but some features were missing (as possibility to block request or use custom scheme url).
I started to focus on Akregator as it still used khtml, I migrated it to QtWebKit and after that to QtWebEngine. (For 16.04 there is a experimental option to activate compilation).
When I proved that it was possible to use in kdepim I started to port kmail. It was not easy as we use specific QtWebKit methods as QtWebElement which are sync method. In QtWebEngine we need to use async method.
So I started to create test application and autotests to validate my changes.
(For example I wanted to make sure that scamdetection works in QtWebEngine as it worked in QtWebKit).
Status in master
Akregator/Kontact/kmail can use QtWebEngine.
I created a new lib to replace composereditor-ng, named composereditorwebengine to make it possible to use QtWebEngine in Blogilo too. I finished it this morning.
I reimplemented AccessKey + AdBlock + ScamDetection support against QtWebEngine.
I will continue to fix, implement features. Not all is finished (but I use by default KMail QtWebEngine so I can see bugs and fix them).
Recent Posts
Select Month
August 2016
April 2016
March 2016
January 2016
December 2015
November 2015
October 2015
August 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
September 2014
August 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
January 2011
December 2010
October 2010
September 2010
August 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
Categories
March 2016
78910111213
14151617181920
21222324252627Hello,does anybody now if and when QtWebEngine will build with VS1025?I build Qt 5.5.0 for win32 64 bit but in th ened there was noqtwebengine build.I discovered qtwebengine\tools\qmake\mkspecs\features\functions.prfand added win32-msvc2015to the line linux-g++*|win32-msvc2013|macx-clang: return(true)so it trys to start the build but fails in gyp.using python: c:\python27\python.exe version: 2.7.9Using extra options found inc:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\core\qtwebengine_extras.gypiUpdating projects from gyp files...Traceback (most recent call last):File"C:/RTIL/Shared/Qt/5.5.0/qt-src/qtwebengine/tools/buildscripts/gyp_qtwebengine",line 167, in &module&sys.exit(gyp.main(args))File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\__init__.py",line 525, inmainreturn gyp_main(args)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\__init__.py",line 510, ingyp_maingenerator.GenerateOutput(flat_list, targets, data, params)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 2420, in GenerateOutputconfig_name)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 2325, in GenerateOutputForConfigtarget = writer.WriteSpec(spec, config_name, generator_flags)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 471, in WriteSpecspec)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 870, in WriteSourcesprecompiled_header, spec)File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 941, in WriteSourcesForArchfor i in include_dirs])File"c:\rtil\shared\qt\5.5.0\qt-src\qtwebengine\src\3rdparty\chromium\tools\gyp\pylib\gyp\generator\ninja.py",line 312, in GypPathToNinjaassert '$' not in path, pathAssertionError: $(VSInstallDir)/VC/atlmfc/includeProject MESSAGE: Running gyp_qtwebengine"C:/RTIL/Shared/Qt/5.5.0/bld/WIN32-VS14-64/qtwebengine/src/core" -Dqt_cross_compile=0 -D qt_os="win32" -I config/windows.gypi -Dqtwe_chromium_obj_dir="C:/RTIL/Shared/Qt/5.5.0/bld/WIN32-VS14-64/qtwebengine/src/core/Debug_x64/obj/src/3rdparty/chromium" -Dperl_exe="perl.exe" -D bison_exe="bison.exe" -D gperf_exe="gperf.exe" --no-parallel -D qt_gl="opengl" -D disable_nacl=1 -D remoting=0-D use_ash=0 -D disable_glibcxx_debug=1 -D remove_webcore_debug_symbols=1 -D win_release_extra_cflags=-Zi -Dtarget_arch=x64...Project ERROR: -- running gyp_qtwebengine failed --What to do here?$(VSInstallDir)/VC/atlmfc/include is there i even set VSINSTALLDIR byhand without success.Regards,Gunnar Roth
Raw Message
Hello,does anybody now if and when QtWebEngine will build with VS1025?When Chromium starts supporting building with VS2015. So far it doesn't lookslike it will be in 5.6`Allan
Raw Message
Hmmm ok, but for me it looks lije it is supported in master,/chromium/src/+/master/build/vs_toolchain.py1. def_VersionNumber():2. """Gets the standard version number ('120', '140', etc.) based on3. GYP_MSVS_VERSION."""4. ifos.environ['GYP_MSVS_VERSION']=='2013':5. return'120'6. elifos.environ['GYP_MSVS_VERSION']=='2015':7. return'140'8. else:9. raiseValueError('Unexpected GYP_MSVS_VERSION')Regards,GunnarHello,does anybody now if and when QtWebEngine will build with VS1025?When Chromium starts supporting building with VS2015. So far it doesn't lookslike it will be in 5.6`Allan
Raw Message
They are working on it. The first step in working on it is detecting it.`AllanHmmm ok, but for me it looks lije it is supported in master,/chromium/src/+/master/build/vs_toolchain.py2. """Gets the standard version number ('120', '140', etc.) based on3. GYP_MSVS_VERSION."""5. return'120'7. return'140'9. raiseValueError('Unexpected GYP_MSVS_VERSION')Regards,GunnarHello,does anybody now if and when QtWebEngine will build with VS1025?When Chromium starts supporting building with VS2015. So far it doesn'tlooks like it will be in 5.6`Allan
Loading...