Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Jens_E_
New Contributor I
182 Views

Building a custom mkl dll with VS2015 solution; MKL 2018.1.156

Hi,

I am using the provided tool (mkl/tools/builder) to build a custom mkl redist dll for my application. Everything builds and links as expected.

However, it appears my application now requires the microsoft c++ _debug_ runtime libraries.

I inspected the project properties of the libintel64 lp64_parallel project (which is the one relevant for me), in Release mode. I notice that under Linker->Input, the files "vcruntimed.lib" and "ucrtd.lib" are listed. Should this be corrected to "vcruntime.lib" and "ucrt.lib" (without the "d") ?

Note I have tested this and it seems to correct the issue.

Jens

0 Kudos
3 Replies
Gennady_F_Intel
Moderator
182 Views

Jens, do you mean you built the release mode in that case?

Jens_E_
New Contributor I
182 Views

Yes. 

Gennady_F_Intel
Moderator
182 Views

You are right, using "vcruntime.lib" and "ucrt.lib for release mode is the right choice. Regard to VS solution - we will fix this issue into the next MKL 2019 u1. I will keep you inform when this update will be released.

Reply