Quantcast
Channel: Intel® Fortran Compiler for Linux* and macOS*
Viewing all articles
Browse latest Browse all 2583

Why not static linking libiomp5?

$
0
0

Hi,

I'm preparing a dynamic library that I will send to some collaborators. It is loaded and used in Python. 

The library uses OpenMP for parallel computing, thus depends on libiomp5. As the collaborators don't have Intel compiler, I need to ask them to install the redistributable libraries. This makes things more complicated that just sending a .so file.

On the other hand, I've read in several places that it is not suggested to do a static linking to libiomp5.a. For example -static-intel does not affect the OpenMP library and the command to static link openmp has been deprecated.

My questions are:

  • Why isn't it suggested to do a static linking to libiomp5? I mean, everything else you can link (static-intel and MKL), why not this?
  • Could I distribute the libiomp5.so file along with my .so instead of asking them to install the redistributable? It will make things easier. Of course, I know that if they already have libiomp5 installed, it could cause problems. However, I could easily check in my python wrapper whether the library exists and if not, load the one in the distributed with my .so.
  • Same question stand for Windows (as some of my collaborators use windows). Could you mention if there are differences?

Thanks in advance!


Viewing all articles
Browse latest Browse all 2583

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>