The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library
-
I've recently been experimenting with deploying a release built of my first GUI app experiment and I've run into some issues like most people before me.
I have already:
Used
windeployqt.exeinQt\5.15.1\mingw81_64\bin.
I have addedQt\Tools\mingw810_64\binto the Path.
I have manually added the three lib.dll's fromQt\5.15.1\mingw81_64\binto the release folder.Yet I now run into the error that is shown in the title of my post. I've seen a lot of similar errors on the web and I've tried to troubleshoot with the solutions listed there, but I've not seen this error specifically. It's probably not hard to solve, but I've run out of ideas at the moment. It would be greatly appreciated if anyone could give some hints or explanations as to what exactly is going wrong.
-
I've recently been experimenting with deploying a release built of my first GUI app experiment and I've run into some issues like most people before me.
I have already:
Used
windeployqt.exeinQt\5.15.1\mingw81_64\bin.
I have addedQt\Tools\mingw810_64\binto the Path.
I have manually added the three lib.dll's fromQt\5.15.1\mingw81_64\binto the release folder.Yet I now run into the error that is shown in the title of my post. I've seen a lot of similar errors on the web and I've tried to troubleshoot with the solutions listed there, but I've not seen this error specifically. It's probably not hard to solve, but I've run out of ideas at the moment. It would be greatly appreciated if anyone could give some hints or explanations as to what exactly is going wrong.
Hi @Stroopwafel, and welcome!
?open@QDialog@@UEAAXXZ
This symbol is generated by Microsoft Visual C++, not by MinGW.
Make sure you haven't gotten your toolchains mixed up. For example, if you are using the MinGW compiler, you must also make sure that all DLLs in your program (including Qt) were built using MinGW.
-
Hi @Stroopwafel, and welcome!
?open@QDialog@@UEAAXXZ
This symbol is generated by Microsoft Visual C++, not by MinGW.
Make sure you haven't gotten your toolchains mixed up. For example, if you are using the MinGW compiler, you must also make sure that all DLLs in your program (including Qt) were built using MinGW.
@JKSH said in The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library:
Hi @Stroopwafel, and welcome!
?open@QDialog@@UEAAXXZ
This symbol is generated by Microsoft Visual C++, not by MinGW.
Make sure you haven't gotten your toolchains mixed up. For example, if you are using the MinGW compiler, you must also make sure that all DLLs in your program (including Qt) were built using MinGW.
I see. That's strange though as I use MinGW inside Qt Creator as well as the MinGW
windeployqt.exeCould you give me some pointers on where to start checking for sneaky Visual C++ occurrences? I unfortunately don't quite know where to start.
-
First things first: Are you able to build and run your application without errors from within Qt Creator?
-
OK, I'm very sorry for the late reaction. At the moment I can't even get Qt Creator to start....
OK so I've finally got everything working again. It's very slow at the moment but it's at least compiling just fine in both debug from within Qt Creator.
It does not compile in release mode from within Qt Creator... -
@Stroopwafel said in The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library:
Something's very wrong.
You mixed up Qt libraries in your PATH env var.
-
@Stroopwafel said in The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library:
Something's very wrong.
You mixed up Qt libraries in your PATH env var.
@Christian-Ehrlicher said in The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library:
@Stroopwafel said in The procedure entry point ?open@QDialog@@UEAAXXZ could not be located in the dynamic link library:
Something's very wrong.
You mixed up Qt libraries in your PATH env var.
OK After I removed the libraries from the PATH and now I can compile from within Qt again in both Debug and Release mode. I will try to do a Release Deploy soon and report back!
-
@Christian-Ehrlicher You were correct. I could have sworn I set the project up to compile with MinGW but I must have misclicked or some checkmark must have been autofilled on a different compiler. I checked the compiler output today and it clearly states
msvc2019_64. Deploying withwindeployqt.exefrom the\Qt\5.15.1\msvc2019_64\binfolder worked perfectly. This was a good learning exercise.Thank you @JKSH and @Christian-Ehrlicher for the help!
