topic UPDATE: I got this resolved. in Intel® Integrated Performance Primitives

Linking version 8 IPP with Xcode 4.6

Marshall_H_ — Sun, 01 Sep 2013 14:59:45 GMT

I am developing a Macintosh cocoa (objective c) application using xcode 4.6 and the Apple compilers. I setup my project to link to the static (.a files ) IPP libraries. However, when I run the application, the dynamitic IPP libraries try to load and the application fails to run.

Is there any documentation/example projects on how to build xcode 4.6 with IPP version 8? What is the standard method for packaging and shipping an application that uses Intel IPP libraries when I distribute my application?

Note: I have found documentation for using xcode 2 and 3 but none for xcode 4.

http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-for-mac-os-how-to-link-to-the-intel-ipp-for-mac-os-x-libraries-in-application

There is no such article but

Gennady_F_Intel — Tue, 03 Sep 2013 07:49:03 GMT

There is no such article but the pipeline will be the similar. You need take into account that in IPP 8.0 all libraries were renamed: IPP library "_l" and "_t" suffixes removed. A new OS native convention is now implemented: Windows* static libraries now have an "mt" suffix for both single and multi-threaded libraries. Please refer to the Release Note.

I have the same problem.When

Jan_W_1 — Wed, 09 Oct 2013 23:25:00 GMT

I have the same problem.
When I try to statically link the IPP 8 in xcode 4.6 the application fails and says libippcore-8.0.dylib not loaded.
Before when I was using IPP 7 the application worked correctly.

What are the steps to statically link to IPP 8 in xcode 4.6? I'm using the following libraries:
libippcore.a
libipps.a
libippvm.a

I'm using the Apple LLVM 4.2 compiler.
I need to link these libraries without dependencies to other dynamically loaded libraries.

Hi Jan,

Sergey_K_Intel — Thu, 10 Oct 2013 14:29:12 GMT

Hi Jan,

Did you set DYLD_LIBRARY_PATH variable before running the application? Do you have libippcore-8.0.dylib file itself?

Regards,
Sergey

Hello Sergey,

Jan_W_1 — Fri, 11 Oct 2013 10:25:46 GMT

Hello Sergey,

Yes I do have the libippcore-8.0.dylib file but why is that file needed for static linking anyway? With version 7 of IPP I just needed link to the static *.a libraries.

I don't want to have to distribute dylib files with the product.

I am seeing this behavior

gpers — Sat, 15 Feb 2014 03:38:56 GMT

I am seeing this behavior trying to statically link IPP 8.0 from XCode 5. Was this ever resolved?

Hello,

Pavel_B_Intel1 — Mon, 17 Feb 2014 12:07:28 GMT

Hello,

the best way to link an application with static libraries is point full path+libname in the link string, for example:

g++ -o mytest mytest.cpp -I $IPPROOT/include $IPPROOT/lib/libippi.a $IPPROOT/lib/libipps.a $IPPROOT/lib/libippcore.a

In IPP 8.x we renamed IPP libraries according native OS name convention.

Pavel

From Xcode, I add the libipp*

gpers — Wed, 19 Feb 2014 15:36:11 GMT

From Xcode, I add the libipp*.a files directly from the full path under "Link Binary With Libraries". But when I try to run, I get the error that Library not loaded: ./libippcc-8.0.dylib. Should I be linking a different way?

Quote:gpers wrote:

Soilworker — Wed, 03 Sep 2014 20:06:00 GMT

gpers wrote:

From Xcode, I add the libipp*.a files directly from the full path under "Link Binary With Libraries". But when I try to run, I get the error that Library not loaded: ./libippcc-8.0.dylib. Should I be linking a different way?

I'm having this exact issue. I've also tried every possible permutation of path settings for each .a file under Frameworks (absolute, relative to IPP root, IPP lib directory, etc.) No change in behavior - for some reason it's still trying to link dynamically when all I ever want to do is link statically.

I'm running XCode 5.1.1 in OS X 10.9.4 with Intel IPP 8.2. Any help would be greatly appreciated!

UPDATE: I got this resolved.

Soilworker — Thu, 04 Sep 2014 00:22:00 GMT

UPDATE: I got this resolved. This is purely an XCode issue. Because there is no obvious, explicit way to get XCode to ignore all the .dylib files and use the .a files (even though I explicitly added only the .a files in the build steps), I simply added "dylib" folders inside my lib folders, and moved all the dylibs there (so XCode won't see them with recursion disabled.) Voila, problem solved (albeit inelegantly.)