Intel® IPP- Library dependencies by domain

I want to build an application with the Intel® IPP which domain libraries do I need to link to?

Intel IPP is divided into groups of related functions. Each subdivision is called domain, and has its own header file, static libraries, dynamic libraries, and tests. The table below lists each domain's code, header and functional area.

The only way to know the exact dependencies for the Intel® IPP functions called from your application is to link to the libraries. For example, if your application uses JPEG functions then you must link to ippj.lib (Windows*) or (Linux*). After you link, if there are unresolved symbols to functions with the prefix ippi, this means you also need to link to ippi.lib (Windows) or (Linux). The ippcore library (ippcore.lib for Windows or for Linux) is required for all domains.

The file ipp.h includes Intel IPP header files with the exception of cryptography and generated functions. If you do not use cryptography and generated functions, include ipp.h in your application for forward compatibility. If you want to use cryptography or generated functions, you must directly include ippcp.h and ippgen.h in your application.

Code of Domain

Header file






audio coding

CC ippcc.h ippi

color conversion

CH ippch.h ipps

string operations

CORE ippcore.h ipp

core functions

CP ippcp.h ipps


CV ippcv.h ippi

computer vision

DC ippdc.h ipps

data compression

DI* ippdi.h ipps

data integrity

GEN* ippgen.h ippg

spiral generated

I ippi.h ippi

image processing

J* ippj.h ippi

JPEG compression

M* ippm.h ippm

small matrix operations

R* ippr.h ippr

realistic rendering and 3D data processing

S ipps.h ipps

signal processing

SC* ippsc.h ipps

speech codecs

VC* ippvc.h ippi

video codecs

VM ippvm.h ipps

vector math

E** ippe.h ipps

embedded functionality

* refers to deprecated domain

** available only within the Intel® System Studio suite



Please avoid starting any new projects with the deprecated domains.

For more complete information about compiler optimizations, see our Optimization Notice.