Running a Windows executable with PATH missing the path to a required .dll that’s not on the working directory typically causes error code 0xc0000135 and a popup dialog telling which .dll file is missing.
With CTest (across any version of CMake I’ve used in past couple years), a missing DLL on PATH does not cause this popup dialog to appear (but 0xc0000135 is raised). The solution would seem to be:
ctest --interactive-debug-mode 1
However this does not seem to have any effect. Is this something that broke at some point? Like something that worked on Windows XP or 7 and not on 10?
Having this work (again) would be quite helpful when unit tests fail on user Windows computers.