KDSoap deployment on Windows
-
@Benjamien said in KDSoap deployment on Windows:
When I try to run the application it shows a message saying kdsoap.dll is missing.
Then copy over this dll to the directory with your executable.
-
Can you run your release executable on your development PC? If so then there is also a kdsoap.dll somewhere.
-
How do you link against this library? What import lib do you use?
Try renaming the dll. -
I have changed the Target name for the release build to kdsoap instead of kdsoap2
So now I have a kdsoap.dll but it still doesn't work.
I link to the library with "LIBS += -L/C:\Users\info\Documents\Source\Repos\KDSoap\build\lib\Release\ -lkdsoap"
When I try to run now I get a message "Cannot start (0xc00007b) ..." -
@Benjamien said in KDSoap deployment on Windows:
When I try to run now I get a message "Cannot start (0xc00007b) ..."
Use Dependency Walker to see which dll is missing
-
@Benjamien
As @Christian-Ehrlicher says. Under Windows if you do have a DLL needed by a program, but some dependent DLLs for that DLL are missing, Windows has a way of reporting that the first DLL is "missing", which is a bit misleading. Your "cannot start" error can also be caused by wrong/incompatible versions of various DLLs.On a separate point. Since you say your code does link OK it should not be the issue you are seeing at runtime, but are you sure your
LIBS += -L/C:\Users\info\Documents\Source\Repos\KDSoap\build\lib\Release\ -lkdsoap
really is what you have? I am surprised that would work with the
/
you show in it, but maybe it accepts that in front ofC:
.....