echoscu.exe is asking for dcmtls.dll

[JustSomeGuy]

I wanted to run an echo so I downloaded the latest dynamics binary distribution.
dcmtk-3.6.4-win64-dynamic.zip
(I wished for a static but the luck of the Irish wasn't with me.)

When I run echoscu a dialog pops up and asks for dcmtls.dll
I downloaded dcmtk-3.6.4-win64-dynamic-tls.zip with the hopes of finding dcmtls.dll but what I found was that it contained the dll but it also contained echoscu-tls.exe

So this just seems wrong to me...
I've never been asked for tls dlls before but I am now.

I believe that the build on https://dicom.offis.de/dcmtk.php.en may have been built with a wrong flag.
Can you point me to a static build or to a build that doesn't require a dll it isn't intended to use?

[Jan Schlamelcher]

That seems strange. Release 3.6.4 was build using the same script we used for building 3.6.3, so, I would not expect a different behavior. We don't provide static libraries since they turned out awfully big since after the introduction of various new modules etc. The DCMTK without TLS might also have a stub dcmtks.dll that contains the symbols without an actual implementation, perhaps it is missing in the package (no idea how that might come to be though)?

[JustSomeGuy]

I agree it's odd.. but more importantly i think it's wrong.
Is it within my power to fix this or should Offis be checking the build to see if there is an issue?

[J. Riesmeier]

The file dcmtls.dll is part of the dcmtk-3.6.4-win64-dynamic.zip package -- I just re-checked that.

[Jan Schlamelcher]

So, if it is there, it should also be found, right? As far as I know Windows always looks into the directory next to an executable for any required DLL, maybe this is now configurable on Windows 10 and you disabled it? Otherwise I have no idea how could come to observe this behavior.

[J. Riesmeier]

So, if it is there, it should also be found, right?

This is at least true for my Windows 7 system.