| Summary: | Revision 85957712044d7a91d3ee4eec4012c333cd7fe70e breaks finding qmake on Fedora with qt3-devel installed | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Kevin Kofler <kevin.kofler> |
| Component: | Build tools: QMake | Assignee: | kdevelop-bugs-null |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | jgrulich, mail, rdieter |
| Priority: | NOR | ||
| Version First Reported In: | 5.0.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=1432726 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Kevin Kofler
2017-03-16 02:56:50 UTC
there's no way we can make it right for all platforms, I'm afraid. When you install a custom Qt into /opt and put it into your PATH, it's qmake will be the right one. So I think keeping the order we have is correct. If at all we could try to run the qmake we found and see if it's at least version 4 and if not then continue. > I'm afraid. When you install a custom Qt into /opt and put it into your PATH, > it's qmake will be the right one. Who says that the user doesn't want to use the distro Qt instead? IMHO, the distro Qt is always the right one if something else was not explicitly requested. It is the one most likely to just work. > If at all we could try to run the qmake we found and see if it's at least > version 4 and if not then continue. For the record, that's what CMake does. Doing what cmake does sounds fine to me. And to your claim that "the distro Qt is always the right one" - that is completely wrong. In my work for KDAB I see tons of Linux based Qt projects, and only the minority of those rely on the distro Qt. Most instead use a specific Qt version built into /opt or elsewhere. Especially for embedded projects, people often even put the SDK's qmake into their PATH. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Updated link to the offending commit: https://invent.kde.org/kdevelop/kdevelop/-/commit/85957712044d7a91d3ee4eec4012c333cd7fe70e The bad code is now in a new location: https://invent.kde.org/kdevelop/kdevelop/-/blob/master/plugins/qmakemanager/qmakeconfig.cpp but still using the same wrong algorithm to find qmake. And plugins/qthelp/qthelpqtdoc.cpp now has its own code to find qmake, with the same bug. |