DLL entry point problem, using the same dll's from the same path as qt creator

[J.Hilk]

@jwall141 well yes, you'll have to use the correct windeployqt tool. There's one for each precompiled Qt Lib you installed.

And delete the old ones! It does not necessarily replace them

[jwall141]

@j-hilk I did delete them, and I only have qt for mingw32 and mingw64. The dll's that windeploy copies are the same (at least the exact same size, i doubt different targets have the exact same size) as the ones in the mingw73_32 folder. I've searched my qt installation path for other Qt5Core.dll and the only ones are for mingw32, mingw64 and qtcreator. I searched the whole system for qt dll's and none of them are in my path. Nevertheless, as i said before, windows tells me the path of the dll that it has problems with, and it's the same as configured in the build environment.

Also the forum lets me reply only every ten minutes, sorry.

[J.Hilk]

@jwall141
I upvoted you, so you should be able to post more regulary

can you post your windeployqt call?

[jwall141]

>windeployqt rfidTagger.exe
C:\companyname\Pruebas\Qt\rfidTagger\release\rfidTagger.exe 32 bit, release executable
Adding Qt5Svg for qsvgicon.dll
Direct dependencies: Qt5Core Qt5Widgets
All dependencies : Qt5Core Qt5Gui Qt5Widgets
To be deployed : Qt5Core Qt5Gui Qt5Svg Qt5Widgets
Updating Qt5Core.dll.
Updating Qt5Gui.dll.
Updating Qt5Svg.dll.
Updating Qt5Widgets.dll.
Updating libGLESV2.dll.
Updating libEGL.dll.
Updating D3Dcompiler_47.dll.
Updating opengl32sw.dll.
Updating libgcc_s_dw2-1.dll.
Updating libstdc++-6.dll.
Patching Qt5Core.dll...
Creating directory C:/companyname/Pruebas/Qt/rfidTagger/release/iconengines.
Updating qsvgicon.dll.
Creating directory C:/companyname/Pruebas/Qt/rfidTagger/release/imageformats.
Updating qgif.dll.
Updating qicns.dll.
Updating qico.dll.
Updating qjpeg.dll.
Updating qsvg.dll.
Updating qtga.dll.
Updating qtiff.dll.
Updating qwbmp.dll.
Updating qwebp.dll.
Creating directory C:/companyname/Pruebas/Qt/rfidTagger/release/platforms.
Updating qwindows.dll.
Creating directory C:/companyname/Pruebas/Qt/rfidTagger/release/styles.
Updating qwindowsvistastyle.dll.
Creating C:\companyname\Pruebas\Qt\rfidTagger\release\translations...
Creating qt_ar.qm...
Creating qt_bg.qm...
Creating qt_ca.qm...
Creating qt_cs.qm...
Creating qt_da.qm...
Creating qt_de.qm...
Creating qt_en.qm...
Creating qt_es.qm...
Creating qt_fi.qm...
Creating qt_fr.qm...
Creating qt_gd.qm...
Creating qt_he.qm...
Creating qt_hu.qm...
Creating qt_it.qm...
Creating qt_ja.qm...
Creating qt_ko.qm...
Creating qt_lv.qm...
Creating qt_pl.qm...
Creating qt_ru.qm...
Creating qt_sk.qm...
Creating qt_uk.qm...
Creating qt_zh_TW.qm...

[J.Hilk]

@jwall141 and the path to windeployqt? Did you add one of your Qtinstallations to your PATH?

[jwall141]

@j-hilk

>where windeployqt
C:\Qt\5.13.0\mingw73_32\bin\windeployqt.exe
C:\Qt\5.13.0\mingw73_64\bin\windeployqt.exe

[jsulm]

@jwall141 Use absolute path to windeployqt to make sure you use the correct one

[jwall141]

@jsulm I just tried that. Same issue. I think the problem is somewhere in the compiling of the exe. As i've said before, the error dialog says that it fails to find the entry point for the dll under the folder of 32bit mingw (when the dll's are not there, without running windeploy). That's the compiler I am using according to the kit, with the same version and path. I even checked if the qmake.exe used is the one in mingw folder, and it is.

[jwall141]

@jsulm I'm currently installing version 5.12.4 to check if it works. Will update.
I'm forced to use 32 bits, since i need to use an sdk for some hardware i'm working with that comes as 32bit dlls.

Update: Same issue with 5.12.4

[jwall141]

@jsulm half solved. Added mingw qt folder path to the system environment path (previously it was only on the user environmet). Now i can run the program outside of qt creator without any dlls in the folder.

But, when i execute the right windeployqt, the dlls that it copies are not right, i get the entry point error again

[J.Hilk]

@jwall141 well, than there's only one way.

Run the deploy tool and manually replace the dlls with the correct ones.
The Deploytool should copy all needed files, even if they are from the wrong wt installation