Custom DLL Linking Issue

Intel® Integrated Performance Primitives

Deliberate problems developing high-performance vision, signal, security, and storage applications.

Custom DLL Linking Issue

514 Views

We are struggling with strange issue related to IPP lib linking.

We have one .Net Exe which uses managed (C#) DLL which interns calls intel custom DLL (C++ unmanaged) through pInvoke.

If we use intel custom DLL with ‘Multi-thread Static Lib’ or ‘Single Thread Static Lib’ it works fine.

But when we use intel custom DLL with ‘Multi-threaded DLL’ or ‘Default Linking Method (which is /MD)’ it does not work as expected.

Following project setting we are using -

Include path: ‘$(INTEL_DEF_X64_INSTALL_DIR)ipp\include’

Lib path: $(INTEL_DEF_X64_INSTALL_DIR)ipp\lib\intel64

No lib name has been added in input lib path.

Could you please tell what exactly we need to do for intel custom lib compile for dynamic lib?

Link Copied

0 Replies

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.