Qt4 going away in Debian

Everything about development and the OpenMW source code.
Post Reply
User avatar
psi29a
Posts: 5356
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Qt4 going away in Debian

Post by psi29a »

https://www.phoronix.com/scan.php?page= ... o-Drop-Qt4
Debian developers are still hoping they will be able to remove the Qt4 tool-kit during the Debian 10 "Buster" development cycle.

While there is still some open and proprietary software continuing to use the Qt4 tool-kit, Debian developers hope they transition soon to Qt5 or another tool-kit.
This means that for Ubuntu and Debian, Qt4 will eventually go away.

Has the issue with Qt5 and OSG/OpenGL context ever been resolved or worked around?
User avatar
MiroslavR
Posts: 156
Joined: 12 Feb 2014, 17:45

Re: Qt4 going away in Debian

Post by MiroslavR »

psi29a wrote: 17 Aug 2017, 09:32 Has the issue with Qt5 and OSG/OpenGL context ever been resolved or worked around?
What issue? Don't see any glaring rendering issues in OpenMW-CS with Qt5 support.
aesylwinn
Posts: 243
Joined: 14 Dec 2015, 20:30

Re: Qt4 going away in Debian

Post by aesylwinn »

Well, this workaround is still in the code, which is what I believe is being referred to.

Code: Select all

#if QT_VERSION >= 0x050000
    // Qt5 is currently crashing and reporting "Cannot make QOpenGLContext current in a different thread" when the viewer is run multi-threaded, this is regression from Qt4
    osgViewer::ViewerBase::ThreadingModel threadingModel = osgViewer::ViewerBase::SingleThreaded;
#else
    osgViewer::ViewerBase::ThreadingModel threadingModel = osgViewer::ViewerBase::DrawThreadPerContext;
#endif
User avatar
psi29a
Posts: 5356
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Qt4 going away in Debian

Post by psi29a »

Thanks guys, I was wondering Scrawl could help here since he was the one I talked to about this years ago when originally creating the Debian packages. If it is no longer an non-issue, then we'll switch to building Qt4 by default... and we should probably abandon Qt4 in our code anyway to move on to Qt5 unless someone has a good reason not too.
Post Reply