Intel® Integrated Performance Primitives
Community support and discussions relating to developing high-performance vision, signal, security, and storage applications.
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
6625 Discussions

unresolved link errors -- one way to eliminate rid of many of the common errors

PaulF_IntelCorp
Employee
121 Views

IPP Link Problem:
Link errors, like the dreadedunresolved external symbol error, keep cropping up and you cannot figure out which IPP lib files should be part of your link list when building your IPP application.

Solution:
By default, the linker only includes, or extracts, those functions, or library members, that your application requests. In this case, it is perfectly acceptable to list ALL the IPP lib files in your link list. Using this approach can significantly simplify your build process bookkeeping. (Caution, a few rules do still apply.)

To learn more, read the following KB article:

Simplified Link Instructions for the IPP Library
http://software.intel.com/en-us/articles/simplified-link-instructions-for-the-ipp-library/

Works for me, does it work for you?

0 Kudos
2 Replies
Chao_Y_Intel
Employee
121 Views

This way makes linkage much easier. : -)
In Linux system, the library order is also important for static libraries. It needs to put *merged.a library after related *emerged.a library, and ippcore.a is put after *merged.a and *emerged.a libraries.

Thanks,
Chao
PaulF_IntelCorp
Employee
121 Views
Chao,

Thank you for that clarification :) I have updated the article to reflect that basic rule of ordering.

Paul

Reply