dynamic linking

[jvandeven]

I note that the static link libraries are scheduled for deprecation. I have used static linking until now, and know how to transfer my code over to the dynamic library versions. I am, however, uncertain how this will affect the users of the software that I write. Presumably they will require a copy of the dynamic library files that my program accesses, but do they need the full library of dynamic link files that comes with Intel Visual Fortran? And where would the library files need to be saved on client computers?

I realise that this question concerns an elementory programming problem, but I have no formal programming training...

Many thanks in advance,

Justin.

[TimP]

The redistributable package corresponding to your compiler should include the necessary dlls and suggested installation path instructions. I recall Steve L touched on this question recently on this forum.
I'm not aware of a move to deprecate all of the static libraries, although there appears to be such a plan with respect to the OpenMP library.
The issue comes up more with the /MD default of the corresponding C/C++ compilers; it's necessary to switch either C++ or Fortran for a combined build so that all use either /MT (which I thought was still recommended) or /MD.

[Steven_L_Intel1]

To clarify, as Tim says, only the static OpenMP library is planned for removal, and the default for that one has been dynamic for a while now.

[jvandeven]

Many thanks for clarifying that I only need to worry about my use of OpenMP in relation to this issue (for now). At present I link to the "Multithreaded" library, which I believe is the static version. Should I prepare for the planned removal of the static OpenMP library, by changing over to the "Multithreaded DLL" library, and - if so - should I use dependency walker to identify the files that will need to be included with the program at redistribution?

As always, thanks for your help and patience,

Justin.

[TimP · Accepted solution]

The change amounts to the removal of /Qopenmp-link:static option, so you would need only to avoid depending on that option or the associated .lib. The default treatment doesn't change.