Unable to run Qt applications in Windows

0
votes

I created an executable of the default MainWindow (changed no code whatsoever) with MinGW GCC, and moved the .exe file from the debug directory to another directory in which I have QtCored4.dll, QtGuid4.dll, and QtNetworkd4.dll.

When I click on the executable, I get the error message:

The procedure entry point _ZN7QWidget8winEventEP6tagMSGPI could not be located in the dynamic link library QtGuid4.dll.

Opening my executable with Dependency Walker gives me the following notifications:

Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module. Warning: At least one delay-load dependency module was not found. Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

I really don't know where I'm going wrong, and would appreciate any help. Thanks!

1
c++qtdllmingwdependency-walker
You you verify that the checksums on the Qt dll's are the same? – Kaleb Pederson
Where did you get the DLLs from? If you built them yourself, what is the configuration? And which settings were used to build the executable? – Daniel S
I've never been able to create a stand-alone executable file using Qt... I'd love to know how to do it if you find out. I've been told you need a license. – user1581100
To me it looks like you have Qt dlls from either a different compiler or different version of Qt. – drescherjm
@NekkoRivera you can compile a stand-alone executable without purchasing a commercial license but your program will have to be distributed under the same license as the Qt libraries: the LGPL. You're allowed to "dynamically link" your proprietary program to Qt libraries, since the LGPL is meant to allow proprietary apps to USE open source libraries. – ICoffeeConsumer

1 Answers

1
votes

You either miss a DLL that is dynamically loaded by QtGuid4.dll (dependency walker should indicate that), or that DLL misses symbols because it is compiled with a a different configuration. Is your executable compiled with debug settings, like the DLLs are? Do you have the "normal" DLLs (no 'd') around, too?