- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Now that I'm working on Windows 7 64 bit with a 64 bit application I sometimes feel on top of the world and all those troubles from the 90's with dll hell are behind me.Until I come to redistribing the Intel Primitives libraries and the MKL libraries.Currently we're a small startup with a wonderful product and I'm the software manager. We have 5 Composer licenses of varying releases and I'm working on getting the license server up and running for a floating license we just purchased. Yes, another few thousand to Intel. Not there yet.I have just spent 9 hours over two days trying to make our 64 bit application work in release build on two varying PCs' with different processors. To say that it's frustrating would be an understatment. Well, I'm a Brit. I got it working eventually but it was unguided and felt wrong. Now, I don't expect to get an answer from this forum as I intend to raise this as a paid for support issue. I don't even expect to get an answer that route either.I've become a blue belt in using dependency walker and debug view but I very much do not appreciate the rather unhelpful FAQs , various PDF's and tons upon tons of caveats with license conditions. We currently evaluate a new Intel based SBC every month to find the one that suits our needs. Making our app work on each one as it comes is very very painful. If there was ever a case for moving to an ARM processor and Linux it's now made.CheersAdrian EdmondsCMosaix Ltd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Right, IPP DLL require two levels DLL : upper level IPP DLL, like ippi-7.0.dll, which can be shown in dependency walker and cpu-specific DLL like ippiw7-7.0.dll.
For upper level IPP DLLs, most of them are following the basic rule as the article:
http://redfort-software.intel.com/en-us/articles/intel-integrated-performance-primitives-intel-ipp-library-dependencies-by-domain/. and Ihe ipp manual give each untion the domain discription. So you can find them easily.
for cpu-specific DLL, please see more about this Understanding CPU Dispatching in the Intel® IPP Library. In general, you distribute all cpu-specific DLL, so the application can run on any cpu type.
Best Regards,
Ying
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
According to your discription, I guess, you must had experienced untold hardships before post them here : dll hell, get license sever up, make 64bit applicaton work on different processor and tremendous unhelpful documentation and more. Each of them seems an huge problem. Here is IPP Forum, could you please tell some details about your problem on IPP library. I'm not sure how we can help but just hope to get the attentions here so more developers can share their views.
Best Regards,
Ying
- 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
[cpp]#include#include int main() { IppStatus myStat = ippStsNoErr; IppMsgCatalog *pMsgCat = NULL; int msgCatOpen = 0; myStat = ippMessageCatalogOpenI18n(&pMsgCat); if(ippStsNoErr != myStat) { printf("Execution continues without ippmsg\n"); msgCatOpen = 0; } else { msgCatOpen = 1; } myStat = ippStsH263MCBPCInterCodeErr; /* Test error code */ if(msgCatOpen) { IppMsg StatMsg; if(ippStsNoErr != ippGetMessageStatusI18n(pMsgCat, myStat, &StatMsg)) printf("Could not get translation message!\n"); else printf("ippmsg-based message: %ls\n", StatMsg); } else { printf("static message: %s\n", ippGetStatusString(myStat)); } ippMessageCatalogCloseI18n(pMsgCat); return 0; } [/cpp]
- 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
- 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
Please take into account that in case of IPP DLLs MS Depends doesn't show IPP Waterfall DLLs. It means,
that if one of those DLLs is missing an application won't start. However, an error message
"No DLL was found in the Waterfall procedure"
should be displayed.
It is not clear why your QT-based application "dies". If you have some logging API it has to be enabled in order to
see where a problem happens.
Best regards,
Sergey
- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting Sergey Kostrov
It means, that if one of those DLLs is missing an application won't start. However, an error message
"No DLL was found in the Waterfall procedure"
should be displayed...
I simply wanted to follow up and this is a screenshot with the error message:
Once again, in case of IPP DLLs MS Depends doesn't show IPP Waterfall DLLs.
Best regards,
Sergey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Right, IPP DLL require two levels DLL : upper level IPP DLL, like ippi-7.0.dll, which can be shown in dependency walker and cpu-specific DLL like ippiw7-7.0.dll.
For upper level IPP DLLs, most of them are following the basic rule as the article:
http://redfort-software.intel.com/en-us/articles/intel-integrated-performance-primitives-intel-ipp-library-dependencies-by-domain/. and Ihe ipp manual give each untion the domain discription. So you can find them easily.
for cpu-specific DLL, please see more about this Understanding CPU Dispatching in the Intel® IPP Library. In general, you distribute all cpu-specific DLL, so the application can run on any cpu type.
Best Regards,
Ying
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- The error message is less than helpful. Perhaps an indication of the missing dll would be a good idea.
- Dependency walker in profile will show and will show missing dlls with a bit of effort. It needs to be run on the target platform though.
- The original question seems to have become lost in the noise.
- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![](/skins/images/872293744008A34B36F8ABF94A46CC66/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page