I've got problems with Qt. A few hours ago, all out of the sudden, Qt 5.0.2 did not update my ui_mainwindow.h header file anymore when I changed something in the designer. I noticed, that when I created a new project for testing purposes, that all of the stuff I created in my normal project UI was now in the ui header file of the new test project - my whole UI compiler was broken. I tried different stuff until I decided to update Qt to 5.2 - and it did not show me any errors anymore, it worked! But still, I can't compile. When I press on Debug now, it gives me the exception 0xc000039 - no matter which project to compile.
Does anyone know how to resolve this?
Related
Context: I recently switched from debian stable to debian testing so I have updated several hundred packages since the last time I used QT creator.
When I create a new project in QT creator I am greeted with many error messages.
For example, here are the errors for the autogenerated main.cpp class in a fresh project:
cstddef:50:10: fatal error: 'stddef.h' file not found
error: variable has incomplete type 'QApplication'
forward declaration of 'QApplication'
unknown type name 'MainWindow'
When I open up previous projects that I know have no errors they also show a whole bunch of similar errors.
However, all of these projects build and run just fine.
What is causing this?
I found the solution to this problem in this bug report.
The libclang-common-8-dev package needs to be installed. After installing this package and restarting qt creator all of the errors went away.
After seeing JShorthouse's answer, I disabled all the Clang related plugins. Then, everything started working like normal after restarting QT creator.
Find the plugins list in the menu under Help->About Plugins...
I have the beginnings of a Qt GUI application created in the Qt Creator IDE. I used the project initially to show off some of the IDE's features, and in the process, I ended up adding a QPushButton, but I later removed it to start building the real program. I also used the "go to slot" feature to show that off as well, which created an entry in the .ui file which I removed after removing the button.
The issue then is, whenever I launch the program, I get the following error in my IDE console:
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()
All while the object pushButton does not exist anywhere in my code. I sent the project to a friend to load into his IDE, and the error was not present. I have no idea what's causing this, or if there's a cache I need to clear.
My QT5.1.1 project used to build with qt creator but when I came into work today it no longer worked. To my knowledge, nothing has changed since the last time I was on. A co-worker needed to use my workstation earlier this week and says that he did not change anything.
The error shows up as:
[ui_mainwindow.h] Error -1073741515
I did a Google search and tried a few things.
This page said to try a clean build and run qMake then rebuild. This did not work even after trying multiple times.
This page led to the suggestion of adding QT += widgets to the .pro file (although I did not believe this would work I tried anyways)
I also tried closing the project and re-opening it. I deleted the build directory and that didn't work either.
EDIT:
I added error code 135 because according to this answer on stack overflow the two are related. I have not encountered or seen this error code come up. I have downloaded the dependency walker but I am not sure how to use it.
After a clean start up I get the following pop up when opening a project.
Image of error pop up
It turns out that a coworker accidentally moved a bunch of DLLs out of my MinGW bin directory. I had to move them back.
I'm trying to use QT Creator for an open-source project I downloaded from github.
After some fuddling around I managed to get the project to compile in QT Creator and run in debug mode.
However, I have an issue : strangely the breakpoints that I set are only available for that instance for the debug run for QT Creator. When I stop the debugging, and relaunch the debugging, the previously stated breakpoints are still there, but they are no longer valid. (meaning Qt Creator skips over them). I've verified that new breakpoints are still valid - it's the old ones that become invalid even though they are still listed.
I did not even update any code, just added breakpoints, hit debug and the old breakpoints became invalid even though they are still showing.
No sacarsm intended, but is this a "feature"? If so, how do I turn it off?
If not a feature, what can I try?
It's very painful to re-add breakpoints every time I run a debug.
Using Mac OSX 10.9 here, Qt 5.2, with Qt Creator 3.0 for Mac.
Thanks.
EDIT : Some more info. I realised that whenever the breakpoint works, it has a tiny hour glass next to it, like in the picture. What does the hour glass mean? It could just be something dumb that I'm not doing....
in the end I filed a bug with Qt Creator. For those interested pls check here.
https://bugreports.qt-project.org/browse/QTCREATORBUG-11184
When I launch a basic Qt app within Eclipse, it crashes with a ".exe has stopped working" error.
The context :
its the basic app obtained when creating a Qt GUI project (with a MainWindow), nothing was changed in it, haven't even added a button
PATH has all the necessary stuff (mingw, msys, qt)
project properties and eclipse paths should be ok too (c++, qt, mingw)
the .pro file is ok, no file missing
clean & rebuild, as well as relaunching eclipse doesn't resolve the problem
upon compilation there is no error, just an ignored "cannot lstat `ui_.h': No such file or directory". No relevant result found when searching around that.
if launched, stops with the afforementionned error. Details show its the app that crashed, with error code c0000005, offset 00002cb20. Search results tells me c0000005 is access violation, but where would that come from ? It's the basic app...
tried to launch with eclipse being in admin mode to prevent accesss violation, didn't help
if launched in debug mode, stops with error "Can't find a source file at ../mingw/main.c". I thought I forgot something when I installed mingw, so I did its setup again, but that did not create that file. No relevant search results here either.
my setup: eclipse classic x32 with c++ & php stuff, qt 4.8, win7 x64
I'm getting lost here. I already worked with Qt under Eclipse before (on winXP and vista), got my bunch of installing problems but this one is a first. Anybody went through this already ? Any leads on how to find where the access violation is happening ? Reading this question makes me think it's a Qt Eclipse Integration problem, but how can I circumvent that ?
Thanks for any leads !
Your project doesn't have a TARGET = set in the .pro file. This was probably caused by an Eclipse/Qt plugin wizard screw up, so just typing a new target may not work, other files may have to be renamed manually.
FWIW development on the Qt plugin for Eclipse was halted some time ago, building outside of Qt Creator is definitely one way of making life more difficult for yourself.