- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All ,
I download the IPP beta for MacOS , and install in my Intel-Mac
. The Intel_IPP.framework has been installed on /Library/framework/
. But when i add this framework into my XCode project . there is one link error. Cann't locate the framework for : -framework Intel_IPP . is there one demo to show how to use the Intel_IPP.framework in XCode or other compiler .Thanks very much .
^-^
Ann
I download the IPP beta for MacOS , and install in my Intel-Mac
. The Intel_IPP.framework has been installed on /Library/framework/
. But when i add this framework into my XCode project . there is one link error. Cann't locate the framework for : -framework Intel_IPP . is there one demo to show how to use the Intel_IPP.framework in XCode or other compiler .Thanks very much .
^-^
Ann
Link Copied
- « Previous
-
- 1
- 2
- Next »
25 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No but I stop working on it ...
Thanks.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ann chen:
The Intel_IPP.framework has been installed on /Library/framework/
. But when i add this framework into my XCode project . there is one link error. Cann't locate the framework for : -framework Intel_IPP . is there one demo to show how to use the Intel_IPP.framework in XCode or other compiler
The reason this does not work is that Intel have not created a proper framework. There should be a file /Library/Framework/Intel_IPP.framework/Intel_IPP, but they have not created it. You will not be able to use the IPP in Xcode like a normal framework should be used until Intel correct this error and ship a new version of the IPP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
cialz79:
I've have the same problem. Posted it into premier area and nobody could help me!!!
I can't run my AudioUnit plug-in
I've already purchased IPP 5.1 for Mac 'cause I want to use static linking, why IPP tries to link dynamic libs???
The solutions presented in this thread will only work for applications that are run inside Xcode.
Meaning: there is no solution for a plugin (AudioUnit, VST, RTAS, or other)
AND, there is no solution for shipping an application to an end-user who will run it outside Xcode.
Premier Support are completely unprepared for Mac OS X. They have many questions about how to properly use Xcode, so I sent them to Apple Developer Support, but there has been no progress for several months.
The IPP does not provide static libraries. Those would end with the .a suffix.
Instead they provide shared libraries inside a directory which uses the .framework naming convention, but which is missing the required components to make a proper framework that would work.
I would like to know if there is a single shipping application based on the IPP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also having problems with the Intel_IPP framework for MacOS.
I agree with the other posters that there is a problem with Intel's framework for the evaluation. Why does the DYLD_LIBRARY_PATH environment variable have to be set for this framework, when none of the other frameworks I have used require this? Though this technique works with XCode apps, it makes creating things like plugins very difficult, if not impossible. Where are we supposed to set the DYLD_LIBRARY_PATH environment variable if there isn't an executable associated with the project (such as in a plugin)?
On a related note: The .dylib files that are distributed with the evaluation version appear to have been created incorrectly. The path to the .dylib needs to be specified by the makefile when Intel compiles the IPP libraries, using the -install_name directive. For example:
libtool -install_name /Library/Frameworks/Intel_IPP.framework/Libraries/libippcore-5.1.dylib
Unfortunately, we as users can't fix this ourselves, since we can't change the internal path of the library ourselves.
My question is, is this problem fixed in the licensed shipping version of the OS X libraries?
I agree with the other posters that there is a problem with Intel's framework for the evaluation. Why does the DYLD_LIBRARY_PATH environment variable have to be set for this framework, when none of the other frameworks I have used require this? Though this technique works with XCode apps, it makes creating things like plugins very difficult, if not impossible. Where are we supposed to set the DYLD_LIBRARY_PATH environment variable if there isn't an executable associated with the project (such as in a plugin)?
On a related note: The .dylib files that are distributed with the evaluation version appear to have been created incorrectly. The path to the .dylib needs to be specified by the makefile when Intel compiles the IPP libraries, using the -install_name directive. For example:
libtool -install_name /Library/Frameworks/Intel_IPP.framework/Libraries/libippcore-5.1.dylib
Unfortunately, we as users can't fix this ourselves, since we can't change the internal path of the library ourselves.
My question is, is this problem fixed in the licensed shipping version of the OS X libraries?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
we are sorry for inconvenience due to improper implementation of IPP installation package. This willbe solved in IPP 5.2 beta which comes just in several weeks.
Thanks,
Vladimir

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »