I am working for a project where we deploy the compiled code together with the required dlls instead of relying on installing the full runtime library on the target machines.
I wanted to signal some peculiar behaviour I noticed when upgrading from 2023.1 to 2024.2 with respect to the dependency of executables on the libmmd dll.
I am compiling the code with VS 2022 v17.9.6 on Win11.
With 2023.1 (IFORT), the dependency logic was easy and intuitive:
- executables compiled in Release mode depended on libmmd.dll
- executables compiled in Debug mode depended on libmmdd.dll
With 2024.2 (IFX), executables compiled in both Debug and Release modes seem to depend on libmmd.dll, so the non-debug version of the lib. This can be seen when inspecting the binary file with Dependencies. Indeed, the code only runs when the libmmd.dll is available, both when compiled in Debug and Release mode.
With 2024.2 (IFORT), the executables compiled in Debug mode seem to only depend on the debug version of the library (libmmdd.dll), as before (and as shown by an inspection with Dependencies). However, the code complains about a missing dll and does not run until the non-debug version of the dll is available as well as the debug version. In 2023.1 the debug version was sufficient.
Is this the expected dependency behaviour or is something off in 2024.2?
Many thanks in advance for any feedback.
