• Overview
• Dynamic linkage
• Custom dynamic linkage
• Single processor static linkage
• Static linkage with dispatching
• Quick comparison of the four linkage models

Overview

The Intel® IPP is organized by 3 types of library files:

These libraries offer various linkage models for different needs. The following are the four linkage models supported by the Intel IPP:

• Dynamic linkage
• Custom dynamic linkage
• Single processor static linkage
• Static linkage with dispatching

Steps to quickly demonstrate each linkage model are listed below. This code is used to illustrate the different linkage models:

#include "ipp.h"

int main( )
{
const int SIZE = 256;
Ipp8u pSrc[SIZE],pDst[SIZE];
int i;

for (i=0; i<SIZE; i++)
pSrc[i] = (Ipp8u)i;

ippsCopy_8u(pSrc, pDst, SIZE);
return 0;
}

Dynamic linkage

1. Include ipp.h or corresponding domain include files in your code.
2. Link to ipps.lib from directory \stublib .
3. Before executing the .exe file, ensure the path environment is set correctly. Please run the ippenv.bat from directory \tools\env or run the Runtime Installer from directory \tools\runtime\installer to ensure this application built with Intel IPP dynamic libraries will load the appropriate processor-specific DLL.

Custom dynamic linkage

1. Copy the function names of all Intel IPP functions used from the Intel IPP files into the file export.def. For our code example the content of this file is:

   EXPORTS
   ippsCopy_8u

2. Write a DLL initialization function called DllMain in mydll.c, and call the function ippStaticInit inside of DllMain to initialize the dispatching mechanism
3. Compile mydll.c as a dynamic link library and link it against ippsemerged.lib , ippsmerged.lib and ippcorel.lib . The import library mydll.lib will be generated automatically.

//=========== mydll.c======================
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <ipp.h>

BOOL WINAPI DllMain(HINSTANCE hinstDLL,
DWORD fdwReason, LPVOID lpvReserved)
{
switch( fdwReason )
{
case DLL_PROCESS_ATTACH:
ippStaticInit();
break;
default:
hinstDLL;
lpvReserved;
break;
}
return TRUE;
}

There is another way to create a custom DLL that allows more customization. You can define CPU specific code for your targeted processor. For example “w7” code is for Intel® Pentium® 4 processor. Please refer the latest updated customdll samples from Intel IPP samples directory:
\ipp-samples\advanced-usage\linkage\customdll

Single Processor Static Linkage

In this example, our target system processor is an Intel Pentium 4 processor:

1. Add the file ippsmerged.lib to your project and its source tree.
2. Include ipp_w7.h for Intel Pentium 4 processor, this inclusion must be before the other Intel IPP header files.
3. Add the file ippcorel.lib to your project and its source tree.
4. Include ipp.h as normal, after the header ipp_w7.h.
5. Call Intel IPP functions normally from your application.

Static linkage with dispatching

1. Include ipp.h or corresponding domain include files. It is recommended to include ipp.h instead of any particular domain header file due to dependencies.
2. Before calling any Intel® IPP functions, initialize the static dispatcher by calling ippStaticInit , which will perform the complete dispatching process. Without calling this function, you will run “px” code libraries instead of the optimized version of the code.
3. Link the ippsmerged.lib, ippsemerged.lib and ippcorel.lib from directory \lib.
4. Execute the .exe file; it will execute the appropriate processor code.

Quick comparison of the four linkage models

For more information about the above linkage models, please refer to the Intel® IPP white paper Choosing the best Intel® IPP Linkage Models for Your Applications.

Operating System:

Windows* XP Professional x64 Edition, Windows Server* 2003 Standard x64 Edition, Windows Server* 2003 Enterprise x64 Edition, Mac OS*, Windows* XP 64-Bit Edition, Windows* XP Professional, Windows* XP Home Edition, Red Hat* Linux 8.0, Red Hat* Linux Advanced Server 2.x, Windows Server* 2003, Red Hat* Linux 9.0, Red Hat* Enterprise Linux 3.0, SUSE* Linux* 8.2, Windows Server* 2003 Standard Edition, Red Hat* Linux Advanced Server 3.x, Windows* XP 64-Bit Edition Version 2003

This applies to:

Intel® Integrated Performance Primitives (Intel® IPP)