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
private/qmetaobject_p.h: No such file or directory #39
Comments
This should fix it. Thanks for the heads up. |
It works! Thank you :) |
I have the same problem i am on debian 7 wheezy i have installed qt 5.2.1 but its in /opt/Qt5.2.1 |
Here are general rules that I have sketched for separately installed Qt. Assume that it was installed in ~/Qt5.2.1/
and re-login.
edit
Don't forget to change path_to_your_Qt_directory. Then try to run
|
It works, thanks. |
@ZiDoMs @sshikaree I also have done that way just once upon a time, but I learned it was best to set These days I use an alias setupqt53='export PKG_CONFIG_PATH=/opt/qt/5.3.0/linux/lib/pkgconfig; export CGO_CPPFLAGS="-I/opt/qt/5.3.0/linux/include/QtCore/5.3.0/QtCore"' So I just have to "run" |
Another thing that I do for linking with Qt 5 for my apps is setting up |
@oblitum i agree with you setting the CGO_CPPFLAGS is much better |
@niemeyer Don't you think the README could deserve an improvement in the direction of that old PR/discussion? Maybe putting such instructions in another "general" subsection. |
Yep, it is better to put everything in environment variables. |
I just had the same issue again. #57 fixes that. |
@GeertJohan Have you tried to set the environment as everyone is stating here, it woudn't require a patch. |
Yes. |
@GeertJohan I don't know... I concur it's not friendly but including every point release doesn't seems like a solution either. Personaly, I would just state what should be included, and the user would do so by setting the environment, this would work for everyone, let Qt be installed anywhere in the file system, and wouldn't require frequent patches. |
@oblitum We already have an "Everywhere else" section, and we already have sections that mention how to tweak the environment variables. I've added a note there even then. Please feel free to submit an improvement, though.
We can have as many lines as needed to get environments people care about to build out of the box. For the time being, we only need to do this once per release, which will always be trivial on our side compared to the cost of doing the release. In the medium term, I hope to get a patch in the "go" tool that allow us to glob those paths, so we only need them once. #57 is in. |
So, if @ZiDoMs's installation on Debian was a standard one, I mean, without changing installation path on purpose, all Also, I think the notice in the README is still at the same state as that of the time of that old PR. I think I have provided enough information in that discussion, from my point of view at last, on why a simpler and clearer explanation regarding the environment settings could help. |
There's no battle about this. /opt is part of well known standards. That said, there's something not quite right. Debian would not install something on /opt out of the box, so how has Qt landed there? Is that where the upstream packages from the Qt project are being deployed? Can someone with these packages send us the output of these two commands:
Can you please submit a pull request then? |
What I have provided in that one, would be the same content of a new one... I don't know which section such information would fit better for you. As the owner I would just accept the PR, or use it as a basis for a commit, but editing and putting the info where I feel it fits better. |
By that time i was installing qt5 i didn't feel good about installing qt5 in /usr so i changed it to /opt but Maybe you're right i should have installed qt in default installation path
|
@ZiDoMs That doesn't come from Debian, so /opt is probably a good choice. Where did you get that content from? |
@ZiDoMs I still don't feel right about installing from sources straight to |
@niemeyer I run them in my terminal as you asked
|
Ah, I think the battle I was recalling regards |
@ZiDoMs By content I meant the Qt files installed in /opt. |
Oh sorry from qt project Qt 5.2.1 for Android (Linux 64-bit, 846 MB) |
Alright, the change submitted with ef43d86 should sort out this issue definitively. We don't need to maintain the include paths for individual Qt releases anymore. |
Nice. My docs request is dropped for good. |
OS: Archlinux 64 bits
QT version: 5.2.1 (I received an update today. It was ok with the previous version.)
The text was updated successfully, but these errors were encountered: