I’m very happy to announce that Qt 5.7 is now available. It’s been only 3 months since we released Qt 5.6, so one might expect a rather small release with Qt 5.7. But apart from the usual bug fixes and performance improvements, we have managed to add a whole bunch of new things to this release.
In greater detail:
Qt 5.7 has been released along with a fully supported stable Qt3D module, which offers a high-level facility for 3D graphics. It also brings NVIDIA DRIVE CX support and other Qt automotive improvements, Qt QML supports JIT’ing on more platforms, Qt Multimedia now supports Apple tvOS, new free/libre modules: Qt Charts, Qt Data Visualization, Qt Virtual Keyboard, Qt Purchasing, Qt Quick 2D Renderer, etc.
There’s more information in:
https://www.qt.io/qt5-7/
https://blog.qt.io/blog/2016/06/16/introducing-qt-3d/
https://blog.qt.io/blog/2016/06/16/qt-5-7-released/
Edited 2016-06-16 22:21 UTC
Can’t wait to install it on Linux and see if Qt designer’s icons are jacked up.
https://bugreports.qt.io/browse/QTCREATORBUG-15199
It doesn’t speak much to a cross-platform framework if they can’t get icons to work right on Linux.
I’ll report back.
Nope… still busted
I’ve just tried it and those icons in that place of Qt Creator 4.0.2 are correctly seen using the latest Kubuntu Linux, although I prefer saying this in a bug report.
It is like they don’t want anyone to use their stuff.
“The user of your application has to be able to re-link your application against a different or modified version of the Qt library. With LGPLv3 it is also explicitly stated that the user needs to be able to run the re-linked binary on it’s intended target device. It is your obligation to provide the user with all necessary tools to enable this process. For embedded devices, this includes making the full toolchain used to compile the library available to users. For parts licensed under LGPLv3 you are obliged to provide full instructions on how to install the modified library on the target device (this is not clearly stated with LGPLv2.1, although running the application against the modified version of the library clearly is the stated intention of the license).”
Who changes libraries on running apps ? Is that really an issue, you can’t statically link ?
This license issue is doing them more damage and keeps people from using their products.