- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks strange, could you please to take any IPP sample, for example JPEGView, build and run it to see if it has the same issue?
Regards,
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
you got to right place with your issue, but just want to make it clear that not all the problem related to IPP.
First, when I ask you to build any IPP sample to see if there is no such issue I mean you will build it with build scripts distributed with each IPP sample. We test that sample can be built and work on every supported platform before release. So, if you have some throubles with build sample in MSVC studio most probably they are related to your project settings. You can refer to sample's Makefile to see what compiler/linker option you need to reproduce in your MSVC project.
Second, now I see, that this message issued by IPL dispatcher library (do not mix it with IPP libraries) when it can't find and load apropriate processor-specific DLL. Note, we do not support and/or distribute IPL library anymore. If I remember it right IPL provided several libraries: ipl.lib - import library, to be linked in customer application and several DLLs: ipl.dll - which is run-time dispatcher, it means it detects processor at run time and load processor specific DLL which had names like iplpx.dll, iplm6.dll, ipla6.dll and so on. So, if you only have ipl.dll but do not have processor specific DLLs (or they can't be foundthrough PATH environment variable) dispatcher issue that error message. I recommend you to find those old IPL libraries to make your application work in short time. But for the future, I recommend you to move your development to IPP libraries, which have many advantages in comparison with old IPL library. IPP do support many new platform on both Windows and Linux (ia32, em64t, Itanium, Xscale). It provides flexible and low-level API and optimization for the latest Intel processors.
Regards,
Vladimir

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page