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

Build is broken #16

Closed
mxsrc opened this issue Oct 31, 2015 · 7 comments
Closed

Build is broken #16

mxsrc opened this issue Oct 31, 2015 · 7 comments

Comments

@mxsrc
Copy link

mxsrc commented Oct 31, 2015

When cloning the repository and running qmake I get only this output:

Tip: Run qmake HELP=1 for a list of all supported build options

@attente
Copy link
Contributor

attente commented Nov 1, 2015

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'.

@mxsrc
Copy link
Author

mxsrc commented Nov 1, 2015

Oh, you're right. My bad.

@mxsrc mxsrc closed this as completed Nov 1, 2015
@mxsrc
Copy link
Author

mxsrc commented Nov 2, 2015

I still have issues getting it to build properly. When I use something like PREFIX=$HOME/somewhere
I get errors while running make install, apparently some headers are tried to copy to /usr/include and when I circumvent that by manually setting the include dir it tries to copy to /usr/share/qt/mkspecs.
Is this intended?

@jpetersen
Copy link
Member

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.

@attente
Copy link
Contributor

attente commented Nov 2, 2015

I found that setting CONFIG+=local-install in the qmake command line prevented it from installing outside of the PREFIX, for me at least.

@jpetersen
Copy link
Member

Ah yes we have that option for that purpose.

@mxsrc
Copy link
Author

mxsrc commented Nov 2, 2015

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.

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

3 participants