-
Notifications
You must be signed in to change notification settings - Fork 49
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
Build is broken #16
Comments
I think that's only an informational message; after running qmake, the project still generates a Makefile in the top-level directory which you can build the project with by just calling 'make'. |
Oh, you're right. My bad. |
I still have issues getting it to build properly. When I use something like PREFIX=$HOME/somewhere |
It tries to install some stuff into Qt plugin and Qt mkspecs directories. Because that is where Qt/qmake will look for them. But yes for development another solution would be better. |
I found that setting CONFIG+=local-install in the qmake command line prevented it from installing outside of the PREFIX, for me at least. |
Ah yes we have that option for that purpose. |
Ah nice, now it is working for me. I must say though that I find it weird that the prefix is not by default enforced for all files. |
When cloning the repository and running qmake I get only this output:
The text was updated successfully, but these errors were encountered: