Well, some success. The advice from Konstantin about mkspecs/modules
led me to these files (which I copied from our Qt-551 build):
... Qt-562\qtbase\mkspecs\modules\qt_lib_webkit.pri
... Qt-562\qtbase\mkspecs\modules\qt_lib_webkitwidgets.pri
These needed to be edited to point into the Qt-562 directory. (And
something needing to be done, adding ".lib" extension to some things,
became apparent when I ran qmake.exe on our application .pro files).
Our application built. HOWEVER, I'm getting this Qt5WebKitd.dll error
(retyped here) when I run:
The procedure entry point
??4??QVector@VQPointF@@@@QEAA?AV0@$$QEAV0@@Z could not
be located in the dynamic link library
C:\Riverware\tools\Qt-562\qtbase\bin\Qt5WebKitd.dll
This looks to be evidence that we CANNOT actually lift the webkit and
webkitwidgets modules build with Qt 5.5.1 into a Qt 5.6.2 build. (I was
kinda surprised at the suggestion, as I understood that binary
compatibility was assured only between different patches within a minor
release).
On 10/27/2016 12:39 PM, Konstantin Tokarev wrote:
27.10.2016, 21:33, "Phil Weinstein"<[email protected]>:
I may have misunderstood. I thought that I could use the webkit and
webkitwidgets components which had built with Qt 5.5.1 (actually move them into
...) a build of Qt 5.6.2.
But I'm getting the following error when I run the Qt 5.6.2 qmake.exe on our
application *.pro files:
* Project ERROR: Unknown module(s) in QT: webkit webkitwidgets
Can those modules be added to "qmake.exe" after the Qt 5.6.2 configure and
build? (Like, are such modules enumerated in an associated text file?).
Yes, being "known module" for qmake is just a matter of .pri file installation
into mkspecs/modules
You have to install QtWebKit into Qt prefix, or otherwise point QMAKEPATH
environment variable to your installation when running qmake
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest
