Something wrong with qt
-
@SGaist like function "rebuild all"? Yes, it build with 0 errors, but error then will come when i press Ctrl+R
P.S. it's definately about Qt, because when i opened first time, after first error it worked, and after like 15min that error with user64 appear. In between i do basically nothing in my computer.
@Engelard
Given the state you seem to be in (e.g. I don't think you should ever be looking for auser64.lib), I think @SGaist would like to see a completely fresh rebuild done, where there is no chance of it picking up bits of already compiled stuff lying around. Now I'm not expert because I don't use C++/Qt Creator/cmake builds, but you should be able to literally delete anything & everything that is not part of your sources and build again from complete scratch. I know "rebuild all" sounds good enough, but it may not be.I don't know what to tell you to delete for sure, but I don't think you should even start with folders named
debugin existence, they should all get created I imagine during the build process. You don't want.objs,.pchs etc. If you're unsure, you can always precede by copying the whole folder hierarchy somewhere, or copying all the sources into a newly-created hierarchy. It is worth doing all this, because your situation sounds pretty strange....P.S.
and after like 15min that error with user64 appear
Extraordinary!
-
@Engelard
Given the state you seem to be in (e.g. I don't think you should ever be looking for auser64.lib), I think @SGaist would like to see a completely fresh rebuild done, where there is no chance of it picking up bits of already compiled stuff lying around. Now I'm not expert because I don't use C++/Qt Creator/cmake builds, but you should be able to literally delete anything & everything that is not part of your sources and build again from complete scratch. I know "rebuild all" sounds good enough, but it may not be.I don't know what to tell you to delete for sure, but I don't think you should even start with folders named
debugin existence, they should all get created I imagine during the build process. You don't want.objs,.pchs etc. If you're unsure, you can always precede by copying the whole folder hierarchy somewhere, or copying all the sources into a newly-created hierarchy. It is worth doing all this, because your situation sounds pretty strange....P.S.
and after like 15min that error with user64 appear
Extraordinary!
Extraordinary!
It's not time for fun rly. My Qt not working anymore.
P.S. tried to compile other projects i have, they compiled and run as they should. But i did'nt add or remove anything from my project which have error. It's in fact the same as that which i mentioned before.
-
Extraordinary!
It's not time for fun rly. My Qt not working anymore.
P.S. tried to compile other projects i have, they compiled and run as they should. But i did'nt add or remove anything from my project which have error. It's in fact the same as that which i mentioned before.
-
So what can i do? And what might cause such a problem?
UPDATE:
Oh. I just goes to build folder, and in \debug was no output .exe file of this project, seems like something happened when i removed that copy of .exe which was asked first error. But if i put that .exe in \debug folder and try to build project - it deletes that .exe and give save link error.... And now i can't restore that .exe which was removed by Qt. It's not even in Recycle bin...
-
So what can i do? And what might cause such a problem?
UPDATE:
Oh. I just goes to build folder, and in \debug was no output .exe file of this project, seems like something happened when i removed that copy of .exe which was asked first error. But if i put that .exe in \debug folder and try to build project - it deletes that .exe and give save link error.... And now i can't restore that .exe which was removed by Qt. It's not even in Recycle bin...
@Engelard Well, the executable is deleted when you're building because it will be replaced by new one if the build succeeds. You should try to delete the complete build folder, run qmake and build.
-
@Engelard Well, the executable is deleted when you're building because it will be replaced by new one if the build succeeds. You should try to delete the complete build folder, run qmake and build.
-
@SGaist said in Something wrong with qt:
AFAIK, there's only the User32 library provided on Windows.
I searched for this "user64.lib" on PC, nothing found. Searched for such a file to download - also, seems like no such .lib even exist. So why then Qt ask me for that thing which does'nt exist?
-
I just now tried next:
- Found User32.lib on my C:\
- Place it in build directory
- Renamed it to user64.lib
And that stupidity just worked now.
What's wrong with qt? it's certainly should'nt work like that...
Some stupid questions:
Are you the only one having access to that PC?
Is there a chance that someone is trying to play some nasty games with you?
When you are in creator, press "Ctrl+Shift+F" and search all projects for user64 and have a look what pops up.Vote the answer(s) that helped you to solve your issue(s)
-
Some stupid questions:
Are you the only one having access to that PC?
Is there a chance that someone is trying to play some nasty games with you?
When you are in creator, press "Ctrl+Shift+F" and search all projects for user64 and have a look what pops up.@koahnig said in Something wrong with qt:
@Engelard
Are you the only one having access to that PC?Yes
Is there a chance that someone is trying to play some nasty games with you?
Wat? :D
When you are in creator, press "Ctrl+Shft+F" and search all projects for user64 and have a look what pops up.
Found LIBS += -luser64 in my pro file
-
@koahnig said in Something wrong with qt:
@Engelard
Are you the only one having access to that PC?Yes
Is there a chance that someone is trying to play some nasty games with you?
Wat? :D
When you are in creator, press "Ctrl+Shft+F" and search all projects for user64 and have a look what pops up.
Found LIBS += -luser64 in my pro file
-
-
