Skip to content
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

cmake/sip_configure.py: Use of non-standard qmake binary names not completely solved #119

Open
a17r opened this issue Oct 16, 2022 · 0 comments

Comments

@a17r
Copy link

a17r commented Oct 16, 2022

This was already touched in #22 but not really solved.

Whatever you think will be in PATH for qmake, it is not standardised at all prior to Qt6. In Qt6, upstream finally decided to make Qt installable side-by-side using 6 suffix on respective Qt binaries, and they also introduced a distinction on what would be "user-facing" (in PATH) or not (remain in some lib/libexec subdir not in PATH). In Gentoo we decided to do the same with Qt5, we had already done a great deal of work in past years to fix packages not to depend on a random filename pattern search in PATH.

Therefore:
qmake may be any of binary, hardlink, softlink controlled by qtchooser, which may be switched at will to any major Qt version by the user through config file
Qt4 may be qmake, qmake4, qmake-qt4, qt4-qmake, and those are just variants I know of
Qt5 same as above, random across distros.

The cleanest way to solve this is give configure the possibility to have the QTBINDIR injected, which can then be set by distro accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant