-
Notifications
You must be signed in to change notification settings - Fork 5
qmake point to qmake-qt5 on some linux distributions #5
Comments
Is this working in this case? |
Yep that works fine:
PS: I am looking into packaging pygs for the AUR. I can either keep the PKGBUIL in a personal respository or submit it here as pull request when it is ready. What would you prefer? |
Reopening because it actually does not work for PyQt5:
Changing qmake to qmake-qt5 in setu.py/configure.py does not help so this might be another issue... |
Seems like the issue is with the include path. QApplication is defined in QtWidgets not QtGui. This require some fix in the libqxt .pro file (I've never used qmake and .pro files and I am unsure what needs to be changed exactly). |
I edit the .pro file in an attempt to fix this issue, please test it, thanks. As to the PKGBUILD file, after some surveys, I still have no idea where is the proper place for it, so please do it at your convenience 😊. |
Hello. Unfortunately this is not fixed yet. The error is different, now it finds QApplication header but fail to find Here is the relevant error log:
|
What about this? |
Nope 😢
|
If you would like to debug it yourself, you can easily install an archlinux based system using the user friendly derivate: Manjaro Linux (this is actually what I am using) |
Thanks for the advice, please wait for me to download Manjaro Linux and Qt. |
Take your time ;) I am not in a hurry and I am not really impacted by this bug. I am using pygs for a PyQt4 based could music player application. It is not finished yet and I won't package it before a few days ;) |
Is it fixed now? It works under my linux environment. |
Yes it works great! Nice work!
|
Hello,
Today I've tried to build pygs on another arch linux pc (but with gnome instead of KDE4). The issue on that system is that Qt5 is the default Qt framework and qmake actually points to
qmake-qt5
instead ofqmake-qt4
.I've managed to build pygs by replacing
qmake
byqmake-qt4
insetup.py
andconfigure.py
but that is not a proper fix.Maybe we should add a
QMAKE_EXECUTABLE
environement var? (similar to what I did withQT_API
)?The text was updated successfully, but these errors were encountered: