Qt Creator: Windows app can't find external DLLs
-
My app is working fine on Linux and MacOS, and now I'm trying to port it to Windows. After the usual juggling, I've got it to the point where it compiles and links ok, but it won't run because it can't find a couple of external DLLs (for gpgme and hunspell).
I've followed the instructions in the "Third Party Libraries" section of the Qt Creator help files, and the include files and DLLs are all under "src/3rdParty/", and it can find the DLLs when it links, but not when it runs. How can I fix this?Thanks,
.....Ron
-
My app is working fine on Linux and MacOS, and now I'm trying to port it to Windows. After the usual juggling, I've got it to the point where it compiles and links ok, but it won't run because it can't find a couple of external DLLs (for gpgme and hunspell).
I've followed the instructions in the "Third Party Libraries" section of the Qt Creator help files, and the include files and DLLs are all under "src/3rdParty/", and it can find the DLLs when it links, but not when it runs. How can I fix this?Thanks,
.....Ron
@rjmx The DLL files themselves are not used during link. The linkers uses a matching library file (blah.lib or blah.dll.a depending on you tool chain).
For development purposes only you can have Creator run your program with a modified PATH that includes where the DLLs live.
For the end result, deploy the DLL dependencies on to your target run-time machine. They go in the same folder as your executables or into a folder on the system PATH.
-
@rjmx The DLL files themselves are not used during link. The linkers uses a matching library file (blah.lib or blah.dll.a depending on you tool chain).
For development purposes only you can have Creator run your program with a modified PATH that includes where the DLLs live.
For the end result, deploy the DLL dependencies on to your target run-time machine. They go in the same folder as your executables or into a folder on the system PATH.
@ChrisW67 said in Qt Creator: Windows app can't find external DLLs:
@rjmx The DLL files themselves are not used during link. The linkers uses a matching library file (blah.lib or blah.dll.a depending on you tool chain).
For development purposes only you can have Creator run your program with a modified PATH that includes where the DLLs live.
For the end result, deploy the DLL dependencies on to your target run-time machine. They go in the same folder as your executables or into a folder on the system PATH.
Thanks! I’ll try that.
-
C Christian Ehrlicher moved this topic from General and Desktop on