-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anyone tried compiling PyQt5 against this? #16
Comments
My intention is that we maintain backwards-compatibility and PyQt bindings should not need to be rewritten. What error are you seeing? (unfortunately the plugins API is one area where I unintentionally broke compatibility since upstream no longer supports them, but I'd like to get back to a place where the API is unchanged) |
There were a couple of headers that no longer exist. I'll need to try building PyQt again to check which ones, and I can't remember how I did it when I raised this issue. Building PyQt seems to have gotten harder in recent years… |
I can try to build it in the weekend |
Had to make unexpected webkit builds so here we are, using webkit build from this repo today
|
Ah yes, now I remember, it's |
@FabioLolix @PluMGMK I've readded the (now non-functional) plugin APIs in https://github.com/movableink/webkit/tree/plugin-stubs-readded, would you mind trying the PyQt5 build against that? I have it successfully building, but I'm not super familiar with PyQt so not sure how to install/test it. |
I'm behind with other AUR pkgbuilds (31 are out of date) and some issue to report, after that I can |
I also have it working with PyQt6 via https://github.com/movableink/webkit/tree/plugin-stubs-readded-qt6 although it requires a new PyQt6-QtWebKit package as well as changes to qutebrowser itself. (QtWebEngine doesn't exercise much of Qt6 so there are some breaking Qt6 changes that need to be addressed) I'm going to work on getting those sorted though I've never done much with python packaging. |
PyQt6-QtWebKit is here: https://github.com/mnutt/PyQt6-QtWebKit |
Thanks for this! Unfortunately I've had serious problems getting it to work. I'm sure the issues are at my end (possibly even between the keyboard and chair!) but here goes:
GDB log including (long!) backtrace:
|
Hello! First off, thanks to all involved for your efforts to keep QtWebKit alive!
I heard about this from qutebrowser/qutebrowser#4039 (comment) and decided to try it out, but PyQt can't seem to build against it. I started on a road of stripping out references to things like qwebpluginfactory (part of the "Legacy" API?) but didn't get very far, and I'm worried I'd just screw it up entirely if I kept going...
Basically, do the PyQt bindings need to be rewritten for the non-"Legacy" API? I'm not too familiar with it, so I'm not sure what's involved...
The text was updated successfully, but these errors were encountered: