FS#52846 - [qt5-webkit-ng] Does not recognize standard #include <QWebView> directives (and others)

Attached to Project: Arch Linux
Opened by Doug Massay (dougmassay) - Saturday, 04 February 2017, 15:26 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 12 February 2017, 15:20 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Not working at all like a "drop in" replacement for qt5-webkit in my experience. Software that builds fine using the system Qt5.8.0 and qt5-webkit (community) fails when trying to build against qt5-webkit-ng (Preview 4 or 5). First it fails to find the includes for QWebView, QWebPage, QWebFrame using the standard system notation that works fine with qt5-webkit, and even if the source is modified to explicitly point to the needed headers, gcc fails to recognize just about any of the functions from QtWebKitWidgets when linking.


Additional info:
https://github.com/Sigil-Ebook/Sigil/issues/277


Steps to reproduce:
1) Build Sigil using qt5-webkit
2) Build Sigil using Qt5-webkit-ng
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 12 February 2017, 15:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt5-webkit-ng tp5-2
Comment by Antonio Rojas (arojas) - Saturday, 04 February 2017, 20:57 GMT
Problem is that the cmake files are not exporting the necessary include directories. Please report this upstream.
Comment by Doug Massay (dougmassay) - Saturday, 04 February 2017, 21:51 GMT
Done. Thanks.
https://github.com/annulen/webkit/issues/427
Comment by Doug Massay (dougmassay) - Saturday, 04 February 2017, 22:58 GMT
Upstream claims the installed cmake files are exporting the correct include directories.
Comment by Doug Massay (dougmassay) - Sunday, 05 February 2017, 19:43 GMT
Upstream appears to be willing to address this issue in the near future. Should I close this report, or wait to see what happens?
Comment by Antonio Rojas (arojas) - Sunday, 05 February 2017, 19:48 GMT
let's keep this open, this is important enough to warrant backporting

Loading...