Recently we started using MKL as well. It also has a custom build tool.
The problem is the ipp tool links with libiomp5mt.lib and the mkl tool links with libiomp5md.lib, meaning we get an OMP abort error (Initializing libiomp5md.dll, libiomp5mt.lib already initialized).
Reading over the forums it seems both should link with the same thing so I am guessing I have to change one of the custom makefiles.
Is there any reason the ipp and mkl custom build tools link with omp differently??
From what I've been reading to avoidconflicts all components shouldlink with ompdynamically, meaning changing the ipp customdll makefile. Though we are reluctant to do this because we have been using it for years with no problems.
Is there any reason that the ipp custom buildexamplelinks withlibiomp5mt.lib instead of libiomp5md.lib?? Would there be any danger in changing it to use libiomp5md.lib??
Did you referred to this article?
another useful, http://software.intel.com/en-us/articles/openmp-support-change/
Thanks. Everything I have seen recommends dynamic linking with openmp (libiomp5md.lib).
The ipp custom build examples (which we followed) linked with openmp statically (libiomp5mt.lib), but I am going to try changing that to libiomp5md.lib so that we don't end up with two copies of the library, when mkl is used as well. I just wanted to make sure there is no reason that ipp has to be linked statically (libiomp5mt.lib).
I gathered that from the reading I've been doing. Are you going to change the custom build sample?? That is what led us to use static linking to openmp in our custom ipp .dll.
Thanks for your help.