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.)

The IPP lib file link lists shown below should work for building your IPP application. This KB article is based on the v6.1.1 IPP library distribution, version 6.1 update 1 (v6.1.1.xxx).

The link lists below assume a Windows Visual Studio build environment. The basic idea also applies to Windows and Linux makefiles or scripted build environments. For the Linux OS and other operating system build environments you will need to change the extension of your lib filenames to match those for your environment.

- Static Link (thread-safe model):

ippacemerged.lib ippccemerged.lib ippchemerged.lib ippcvemerged.lib ippdcemerged.lib ippdiemerged.lib ippgenemerged.lib ippiemerged.lib ippjemerged.lib ippmemerged.lib ippremerged.lib ippscemerged.lib ippsemerged.lib ippsremerged.lib ippvcemerged.lib ippvmemerged.lib ippacmerged.lib ippccmerged.lib ippchmerged.lib ippcvmerged.lib ippdcmerged.lib ippdimerged.lib ippgenmerged.lib ippimerged.lib ippjmerged.lib ipprmerged.lib ippmmerged.lib ippscmerged.lib ippsmerged.lib ippsrmerged.lib ippvcmerged.lib ippvmmerged.lib ippcore.lib

Note: These library files are located in the lib subdirectory in your IPP install directory. The “thread-safe” model means these libraries are safe to use within a multi-threaded application, even though this version of the library is not multi-threaded.

- Static Link (multi-threaded model):

ippacemerged.lib ippccemerged.lib ippchemerged.lib ippcvemerged.lib ippdcemerged.lib ippdiemerged.lib ippgenemerged.lib ippiemerged.lib ippjemerged.lib ippmemerged.lib ippremerged.lib ippscemerged.lib ippsemerged.lib ippsremerged.lib ippvcemerged.lib ippvmemerged.lib ippacmerged_t.lib ippccmerged.lib ippchmerged_t.lib ippcvmerged_t.lib ippdcmerged_t.lib ippdimerged_t.lib ippgenmerged_t.lib ippimerged_t.lib ippjmerged_t.lib ippmmerged_t.lib ipprmerged_t.lib ippscmerged_t.lib ippsmerged_t.lib ippsrmerged_t.lib ippvcmerged_t.lib ippvmmerged_t.lib ippcore_t.lib libircmt.lib svml_dispmt.lib libmmt.lib libiomp5mt.lib

Note: library files in red are Intel Compiler support files and are needed if you are NOT using the Intel compiler to compile and link your application. The equivalent files on a Linux system are named libirc, libsvml, libimf, and libiomp5. these libraries are required to satisfy Intel compiler optimizations and OpenMP calls used by the IPP library, because the IPP libraries are created using the Intel compiler.

- Dynamic Link:

ippac.lib ippcc.lib ippch.lib ippcv.lib ippdc.lib ippdi.lib ippgen.lib ippi.lib ippj.lib ippm.lib ippr.lib ipps.lib ippsc.lib ippsr.lib ippvc.lib ippvm.lib ippcore.lib libiomp5md.lib

Note: libiomp5md.lib is the Intel OpenMP library file and is used by the IPP libraries to implement multi-threading. The equivalent file is named libiomp5 on a Linux system. These files are located in the stublib directory on a Windows system and in the sharedlib directory on a Linux system. You are not required to use OpenMP in your application when you include this library file, but it is required by some IPP library functions when mult-threading is enabled (the default case). To disable OpenMP threading, within the dynamic libraries, see the ippSetNumThread() function.

IPP Cryptography Library
The IPP cryptography library files are not included in the above lists, since they are not part of the standard product. If you are using the IPP cryptography library you will need to add those library files to your link list. The crypto files are named ippcp*.

About Link List Order
Thank you to my colleague Chao Yu who pointed out that the order of the link list is important for static libraries in a Linux environment, since many of the linkers used in this environment default to operating in a single-pass mode. In this case it is best to order the library files according to the following rule: *emerged.a first, followed by *merged.a and ending with ippcore.a. The lists above have been ordered to reflect that rule.

If you have problems with interdependencies between libraries causing link errors on a Linux system you may need to use the -( and -) options (or equivalent --start-group and --end-group options) with your Linux linker to force multi-pass behavior, at the expense of reduced linker performance.

Additionally, you can repeat the name of a library on the link list to resolve circular dependencies, without resorting to the -( and -) options; by listing a library file a second time after the archive that depends on that key library. The nm command can be used to list the object file names within a specific library archive so you can identify which library is needed to satisfy a missing dependency problem.

Additional Info
Obviously, you must also set your makefile or environment variables to point to the appropriate install directories. See the env and tools subdirectories for your IPP installation for more information or review the articles linked below.

Using Intel® IPP Threaded Static Libraries
Building a Windows* Application Using Intel® IPP
Compiling and Linking with Microsoft* Visual C++* and Intel® C++ Compiler
Error LNK2001: Unresolved External Symbol _ipp*
How to Build an Intel IPP Application
Intel® IPP - Intel® IPP Linkage Models - Quick Reference Guide
Intel® IPP- Library Dependencies by Domain
Intel® IPP - Threading / OpenMP* FAQ

If you have a Windows test machine with a large number of CPU cores that you wish to use for testing performance and compatibility with a lesser number of CPU cores you may be able to use that one machine to test several multicore scenarios. For example, an 8-core machine can be configured to restrict Windows from using all 8-cores, forcing it to use, for example, only 4, 2, or even one core in the machine. This technique can be used to more evenly compare system performance by varying the number of cores on the machine and to verify proper operation or scalability of your software for a variety of multicore configurations.

Note: You will have to modify your BOOT.INI file or Boot Configuration Data (BCD on Windows Vista) to setup a machine for this purpose.

To restrict the number of CPU cores Windows will use on a multicore machine follow these instructions:

1.) Determine how many logical CPUs are in your system. Do this by opening the following registry key:

HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor

There will be one subkey for each logical CPU. The precise number of logical CPUs depends on the number of cores in your processor(s) and whether or not those cores are using Hyper-Threading technology. For example, a four-core machine with Hyper-Threading technology can appear to have eight logical CPUs (two threads per core * four cores = eight logical CPUs or threads).

2.) On a Windows XP system, edit the BOOT.INI file located in the root directory of your boot drive (usually C:).

Find the line in the [Operating Systems] section that boots the Windows system you are using (on systems with multiple Windows boot partitions you must take care to identify the correct line). This line usually looks something like the following:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP" /fastdetect

3.) Add one (or more) lines with the /NUMPROC parameter to create a second boot option that limits Windows to the desired number of logical cores.

For example assuming an eight logical CPU system (eight possible execution threads), you might want to add the following boot scenarios (new text is marked in bold):

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP, 1 core" /fastdetect /NUMPROC=1
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP, 2 cores" /fastdetect /NUMPROC=2
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP, 4 cores" /fastdetect /NUMPROC=4
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP, 6 cores" /fastdetect /NUMPROC=6

This configuration would allow you, at boot time, to choose to boot Windows in 1-threads, 2-threads, 4-threads, 6-threads and "all-threads" modes. Your Windows configuration is identical other than the number of execution threads available.

Note: you should modify each description so you can easily identify the specific boot options at boot time.

For full details of all of the BOOT.INI options see the SysInternals website (now part of Microsoft) at:
http://www.microsoft.com/technet/sysinternals/information/bootini.mspx

To configure your Windows Vista system to include a second boot option you will need a BCD editor. For example, you can use VistaBootPRO (www.pro-networks.org) to create and name additional boot entries in your Vista BCD and then use the Microsoft msconfig tool to configure each of your boot options.

-- Configure the number of threads with msconfig.
-- Use VistaBootPRO to create and name those boot options.

Using msconfig seems to work better than VistaBootPRO to configure boot options. VistaBootPRO is easier to use to create additional BCD boot entries.

  • Complete Word
  • Parameter Info

The Parameter Info feature displays the parameter list for a function to give information on the number and types of parameters. Provided your C/C++ code contains the include statement with the appropriate Intel® IPP header file, to get the list of parameters of a function specified in the header file. 

• Type the function name
• Type the opening parenthesis
• This makes the tooltip with the function API prototype pops up, and the current parameter in the API prototype is highlighted as in figure-2

 



More information about Intel IPP functions - IPP Documentation web page.

How is Intel IPP different from OpenCV?
In addition to computer vision, Intel IPP provides high performance low-level routines for audio, video, imaging, cryptography, speech recognition, signal processing and codecs. These functions are designed maximize application performance on Intel® processor-based workstations and servers.


Which Intel IPP functions are used in OpenCV?
The OpenCV library is an open source library of computer vision functions. OpenCV functions are implemented in two ways: with or without Intel IPP function calls. In the first case, customers need to have the Intel IPP binaries installed in order to take advantage of the Intel IPP optimizations. In the second case, all the functionality is implemented in the OpenCV open source code.


How can I make OpenCV automatically call Intel IPP functions at run-time? How to detect it?
OpenCV provides a transparent user interface to the Intel IPP by automatically loading the Intel IPP libraries at runtime if they are available. For Intel IPP versions 5.1 through 6.1, developers do not need to explicitly link with the Intel IPP libraries.

If you are using Intel IPP version later than 6.1, depending on which OpenCV package you haveinstalled, you may need to check the source code to understand which version of the Intel IPP optimized libraries are automatically loaded. Follow these instructions:

1. Open the file OpenCV\cxcore\src\cxswitcher.cpp. 
2. Go to function cvUseOptimized.
3. Depending on your target system, you will need to modify lines numbers 551, 552, and 553. The numbers in quotes below indicate the Intel IPP versions that OpenCV will check for:

551  static const char* ipp_sfx_ia32[] = {"-6.1", "-6.0", "-5.3", "-5.2", "-5.1", "", 0 };
552  static const char* ipp_sfx_ia64[] = { "64-6.1", "64-6.0", "64-5.3", "64-5.2", "64-5.1", "64", 0 };
553  static const char* ipp_sfx_em64t[] = { "em64t-6.1", "em64t-6.0", "em64t-5.3", "em64t-5.2", "em64t-5.1", "em64t", 0 };

4. Make sure that the latest Intel IPP DLLs are on your system PATH so that they are dispatched at application runtime.
5. Here is small test code to detect if Intel IPP dlls are loaded by OpenCV automatically.

#include <stdio.h>
#pragma comment( lib, "highgui.lib" )
#pragma comment( lib, "cxcore.lib" )
int main(){  

      int NumUploadedFunction = 0;
      NumUploadedFunction = cvUseOptimized(1);
      printf("\t NumUploadedFunction = %d \n\n", NumUploadedFunction);

      const char* opencv_lib = 0;
      const char* add_modules = 0;
      cvGetModuleInfo(0, &opencv_lib,&add_modules);
      printf("\t opencv_lib = %s,\n\t add_modules = %s\n\n", opencv_lib,add_modules);

    return 0;
}//_end_of_file_

      if IPP dll are loaded automatically, the output of detect code is like
      NumUploadedFunction = 144
      opencv_lib = cxcore: 1.0.0,
      add_modules = ippcv-6.1.dll, ippi-6.1.dll, ipps-6.1.dll, ippvm-6.1.dll, ippcc-6.1.dll,

// Let A, B and C be single-channel 8-bit images.
IplImage *A, *B, *C;
// Compute C = (A+B)/2 using an Intel IPP function call
IppiSize size = { A->width, A->height };
ippiAdd_8u_C1RSfs( (Ipp8u*)A->imageData, A->widthStep, (Ipp8u*)B->imageData, B->widthStep, (Ipp8u*)C >imageData, C->widthStep, size, 1 );

• 16u data support for existing functions (arithmetic, statistical, Canny and Distance Transform)
• Camera distortion correction (undistortion, generate matrices for ippi Remap function)
• General pyramids (arbitrary rate and kernel are supported)
• Optical Flow (pyramidal Lucas-Kanade algorithm, copy with subpixel precision)
• Haar Classifier support (apply classifier, integral image, stddev for rectangle)

1. Submit an issue to Intel Premier Support where support engineers can help you with Intel IPP function usage.
2. Start a discussion thread in the Intel IPP User Forum and get help from Intel IPP engineers and the developer community.

You can also refer to the Intel IPP Face Detection sample code, which illustrates how to use Intel IPP to apply a classifier using Haar-like features in face detection algorithm in a Windows* application.

1. Include Intel IPP header file and function calls:

2 .From the Menu bar (or right-click the Project in Solution Explorer) select Intel Parallel Composer » Select Build Component. The setting will link the dynamic library atomatically.

3. In this case, you will link the static library, or Intel OpenMP run-time library libiomp5md.lib, please refer to

Compiling and Linking Intel® IPP with latest version Intel® C++ Compilers .

4. Then Build.

Note:  Add the IPP bin path either in your system environment setting or run ippenv.bat from directory \tools\env before run application in command line.

There are ready IPP sample MSVC projects in <Composer install directory>
i.e C:\Program Files (x86)\Intel\Parallel Studio\Composer\Samples\en_US\IPP\ ipp-samples-image. You can easy to open one in MSVC environment and observe above steps.