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.
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
Works for me, does it work for you?
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.