Additional user-environment error trapping: MKL libraries

[jhaasdyk-au]

Brief description
A user-environment with (some) MKL dll missing can cause adjust.exe to exit without error message.

While the DynAdjust installation instructions detail how to install the MKL libraries, some users (e.g. those without admin rights) may source only nominally required dll as I did recently on one of my machines.

Background
RE: dynadjust-windows-mkl.zip (dynamic link type)
Note: the required xerces-c_3_3.dll is provided with the distribution

If a user runs the dynadjust exe(s) with ONLY those dll provided in the Windows MKL distribution,
then a Windows pop-up error message will indicate that "mkl_intel_thread.2.dll was not found".

Adding ONLY mkl_intel_thread.2.dll to the PATH will result in successful runs of import, geoid, segment, reftran,
but adjust.exe will exit without any error message.
(mkl_core.2.dll and mkl_avx2.2.dll are also required, but the user is not informed of this)

Basic requirements
Consider testing the user-environment for all for all required dll.
Trap missing items as an error and inform user.

Priority
Priority 3 (low)

[daleroberts]

Hi @jhaasdyk-au, since the loading of .dll is done by the operating system, I'm not sure how feasible this is without writing a lot of "search" code that looks through the PATH on startup to try to resolve which is the correct .dll to load. Even then, the dll loading happens before the program can run anything. This might be a bit janky to implement.

[jhaasdyk-au]

Thanks Dale.
Given the small number of such dll required for successful execution, I thought perhaps such a list would be knowable / known.
I anticipated quite a small amount of code to test simply if these exist in PATH (then allow os to select which item).

Barring that, are you surprised to see a silent exit if missing certain dll (vs Windows reporting a warning if missing others?).