Problem with plugins trying to debug
-
Hi.
I am having the following problem: I am trying to debug a Qt app, but I need to do it in a specific directory. I manually copied my app because it did not deploy automatically when I compiled and ran it. I also ran windeployqt myapp.exe, which deployed all the necessary DLLs and plugins. When I try to run my app by double clicking it, it works perfectly, but when I try to run it using Qt Creator, I get some errors.QFactoryLoader::QFactoryLoader() checking directory path "F:/myapp/bin/WIN10_32-Debug/platforms" ... qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
F:/myapp/bin/WIN10_32-Debug/platforms
It is not my working directory, it is where my bin is saved ... In my project it is D:\simus\myapp -
Hi.
I am having the following problem: I am trying to debug a Qt app, but I need to do it in a specific directory. I manually copied my app because it did not deploy automatically when I compiled and ran it. I also ran windeployqt myapp.exe, which deployed all the necessary DLLs and plugins. When I try to run my app by double clicking it, it works perfectly, but when I try to run it using Qt Creator, I get some errors.QFactoryLoader::QFactoryLoader() checking directory path "F:/myapp/bin/WIN10_32-Debug/platforms" ... qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
F:/myapp/bin/WIN10_32-Debug/platforms
It is not my working directory, it is where my bin is saved ... In my project it is D:\simus\myapp@JonexElectronic said in Problem with plugins trying to debug:
In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
This must be set at runtime, not at build time, to get diagnostic output from the application startup.
-
@JonexElectronic said in Problem with plugins trying to debug:
In my build environment, I set QT_DEBUG_PLUGINS to 1, but no information is being given to me.
This must be set at runtime, not at build time, to get diagnostic output from the application startup.
@JonB yes, it is in run settings
-
@JonB yes, it is in run settings
@JonexElectronic
Then you should be getting voluminous diagnostic output, just as everyone else does. Check each of the debugger's "output panes". I believe it goes there from Creator even under Windows, where it may be that diagnostic does not appear on standard output/error. -
@JonexElectronic
Then you should be getting voluminous diagnostic output, just as everyone else does. Check each of the debugger's "output panes". I believe it goes there from Creator even under Windows, where it may be that diagnostic does not appear on standard output/error.@JonB Yes, I should be getting that information. But this only happens to me when I have not run windeployqt on the app. Because if I have run windeployqt, the app does not run and no debug information is displayed.
Any idea??