- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
if I understand correctly that you build custom DLL from IPP libraries? If yes you should use IPP static libraries only to link your custom DLL. It is impossible to build custom DLL from IPP DLLs.
Pavel
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page