packaging a dynamically linked application

[jvandeven]

Apologies, I have no formal programming training, but I have been working on a Fortran application for around 10 years now. Around 3 years ago, I reconfigured the code so that it now makes use of dynamic linking. The code is redistributed to secondary users, and until now I have managed this by using dependency walker to identify the dll's that the program references, and then copying these directly into the root directory of the application. But recent updates associated with Windows are making this increasingly difficult. There must be a straight-forward way of dealing with this problem, and any advice that you could provide would be very welcome. For reference, I use OpenMP, the MKL libraries, and COM for communicating with Excel.

[TimP]

For some time now, redistributable library packages have been offered for ifort as well as Visual Studio. I would think the primary alternatives you have are:
1) continue as you have done in the past
2) switch to asking users to install the redistributable packages
3) static linking of ifort libraries

[jvandeven]

Is it possible to use static linking for some libraries, and dynamic linking for others? Some of the libraries that I link to must be dynamic...

[TimP]

Try listing the specific names of the libraries (in your link step or library dependencies) for which you don't want the linker script to make the choice for you.

[jvandeven]

Many thanks - I have sorted the problem out now.