error in the application output while using qt creator - qt

I have pasted the application output in the below link.please go through it and give me necessary suggestions to get my code working.
https://pastebin.com/xaFEBrDY
The program has unexpectedly finished and crashed.
the code had gtk errors which stated the use of both 2nd & 3rd version but after adding the path and libraries of gtk2 and removing gtk3 gave the above errors. can anyone help me out in knowing, what I have missed. thanks in advance

Related

How to make QtLinguist with Qt5.11 and VS2015 work?

When I first run this option in first picture, I get the error in second picture.
However, if I create a new project with current project's files, this option is working well. I don't know why this happens. Can anyone help me solve this? Thank you so much.
I have search much solutions, but neither did them work for my situation.
The application exited with an error (ExitCode 1)
Qt creating new translation (ts) using Visual gives error - (ExitCode 1)
How to make QtLinguist shipped with Qt 5.9.1 work?
I have fix this problem. Our project list contains one item that its related local file is deleted by others, and I just remove this item. Now everything just be fine. The .tf file is now can produced by Qt tool.

error: Failed to parse qmlimportscanner output

I have a created a fresh QML quick application using Qt 5.3.2 on Mac. When I build it has 2 link errors.
Failed to parse qmlimportscanner output.:-1: error:
[iphonesimulator-debug] Error 66
I have not even made any changes to default application, why do I get these errors and how can I fix it?
I know this question is pretty old, however, as I just encountered the same error and finally managed to solve it: Your Project Path must not contain spaces for qml quick projects on ios.
Please do not ask me how or why this is the case (as it clearly works for desktop or android deployment), but this was the issue for me. After moving the project to a different location (a folder that does not contain spaces) it would run qmake and deploy just fine.

Is it still possible to debug opentap 1.5.0 in eclipse/netbeans?

I followed this tutorial to the letter but all I get are errors after errors what's more, because it's so old there's somewhat of an extra step missing as eclipse asks what type of Java application it is when I try to run it despite the errors. Any help or pointers as to how it's possible to achieve this would be appreciated.
I found out that you could import eclipse project into netbeans as it already contained an eclipse project.

Error building QtCore

I am trying to build QtCore.lib and I get this weird error.
PRJ0019: A tool returned an error code from "MOC kernel\qtimer.cpp"
I am able to build qtmain.lib but not able tp go any further.
moc.exe is available in bin folder and the path is added to my PATH.
kernel\qtimer.cpp file is also present in corelib folder.
Any help in this regard will be appreciated. I am building with Qt-4.5.2 source.
In Qt 4.5.2 moc.exe has some issues. An email I sent to Qt Support mentions it moc'ing files that were not modified. It could have further issues, which could be related to what you are experiencing.
Sorry I can't recall the exact details. To make things worse the link Qt Support had sent me at the time is broken.
They had suggested using 4.5.3. I think we ended up staying on 4.5.1, which we are still using today, although the move to 4.7.x. is occurring as I write this. :)

Adding Qxt plugin to Designer

I'm having a problem with adding the Qxt library to Qt Designer. The error it gives is:
Cannot load library C:/Qt/4.6.2/plugins/designer/QxtDesignerPlugins.dll; The specified module cannot be found.
Any ideas on what the problem is?
Try setting the QT_DEBUG_PLUGINS environment variable to 1 and then try again. This should give you some additional debug output that will help isolate the problem.
Did you check that this file is actually there?
Usually, the problem with designer plugins is that they're installed in the wrong directory, or linked against a different Qt (esp. debug vs. release).
Check that the plugin itself can find all the dlls it depends on. Use depends.exe (Dependency Checker) or maybe FileMon.exe to find out.
The error message can be a bit misleading, as it is the same if any of the primary dlls dependencies are missing too.

Resources