Menu
▾
▴
#109 Qt 4 conflicts with Qt 5
It is a very bad thing that Qt 4 cannot be installed side by side with Qt 5. Arch Linux accomplishes this very well (with a qmake-qt4 and a qmake-qt5).
Currently it is impossible to develop e.g. in MSYS2 Qt Creator a Qt 4 application. Or build something that requires Qt 4 if you have Qt Creator installed.
Discussion
Upgrade the other project(s)? You're going to have to at some point anyway, or else forget about them.
With all due respect, that is the most useless response I have ever read.
There is absolutely no reason whatsoever Qt 4 cannot be installed side by side with Qt 5, and there are a ton of projects using Qt4 still, and they will likely still be using Qt 4 for the foreseeable future.
The fact that installing Qt4 results in the removal of a thing like Qt Creator is just a big fat flaw in the packaging of Qt 4 and 5 within the MSYS2 environment.
I'm sorry to have made it onto one of your "most useless" lists.
As you may have noticed, I didn't close the bug or try to pretend it wasn't a bug. My comment was only a suggestion in-case you had a specific project that required Qt4.
There are 3 people working on MSYS2 part time, we must pick our battles. Hopefully one of the many contributors who also helps out has a need for both Qt4 and Qt Creator to co-exist and will submit a fix, but I suspect that pool of people is small.
Last edit: Ray Donnelly 2014-11-14
rubenvb, a lot of files (binaries and text) need to be patched after Qt install to work it properly. Installing Qt and Qt5 together will break installations as qtbinpatcher modify files by patterns using output from qmake.
@Ray I understand that, and don't expect a fix tomorrow, or even next month, or whatever, but in the case of something like Qt, you can't expect a project to be simply updateable to a new major version. Not to mention legacy code that doesn't want that upgrade to happen at all.
Can't qtbinpatcher then be modified to call qmake-qt4 and qmake-qt5 instead, assuming that at least the paths provided by these qmake's correspond to the actual real installation paths? I have no idea what qtbinpatcher does, and I fully understand the pain a relocatable Qt install (well, a Qt install in a non-standard directory) is.