The procedure entry point cound not be located in the dynamic link library
-
Have you got more than one version of Qt5Core.dll on your system? Maybe you copiled against another version than your program runs against.
-
I am not claiming to know the answer to your problem, just trying to help.
But therefore you should please learn to read carefully and answer questions or else nobody can help you or will be willing to do so! -
Hi,
the version from the path: Qt5.0.2/Tools/QtCreator is the one used by QtCreator binary and (IIRC) is build with MSVS.
You have to use the one, you linked to, which means something like:
[SDKPATH]\Desktop\Qt\4.8.1\mingw\bin\ -
Hi,
the version from the path: Qt5.0.2/Tools/QtCreator is the one used by QtCreator binary and (IIRC) is build with MSVS.
You have to use the one, you linked to, which means something like:
[SDKPATH]\Desktop\Qt\4.8.1\mingw\bin\@giesbert Thank you very much for your help. I had the "The procedure entry point _ZN10QArrayData10deallocateEPS_jj could not be located in the dynamic link library Qt5Core.dll." error message and wasn't sure how to deal with it. I realized I was using only .dll files from the C:\Qt\Tools\QtCreator\bin directory. When I used the .dll files from the C:\Qt\5.4\mingw491_32\bin directory, my issues disappeared. This makes sense since I was using that MinGW instance to do my compiling.
Dependency Walker is still stating that I'm missing these files:
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLLThese are .dll files which some forums tell me are only side problems of something unrelated.
-
@giesbert Thank you very much for your help. I had the "The procedure entry point _ZN10QArrayData10deallocateEPS_jj could not be located in the dynamic link library Qt5Core.dll." error message and wasn't sure how to deal with it. I realized I was using only .dll files from the C:\Qt\Tools\QtCreator\bin directory. When I used the .dll files from the C:\Qt\5.4\mingw491_32\bin directory, my issues disappeared. This makes sense since I was using that MinGW instance to do my compiling.
Dependency Walker is still stating that I'm missing these files:
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLLThese are .dll files which some forums tell me are only side problems of something unrelated.
@Robert-Lech said:
Dependency Walker is still stating that I'm missing these files:
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLLThese are false positives. You can ignore them.
Run Dependency Walker on an official Microsoft product (e.g. C:\Windows\notepad.exe) and you'll see some of these declared "missing" too
-
I confirm dll libraries from C:\Qt{version}\mingw{version}\bin make Qt desktop app work.
