How to Side-by-Side Install the Intel IPP 7.0 Library on Windows

Product Index
Search

Intel® Software Network

Language:
- English

	May 9, 2011 12:00 AM PDT

This article describes the key steps you should be familiar with if you are doing a side-by-side install of the Intel® IPP Library, version 7.0 for Microsoft* Windows* on your development system. In other words, if you wish to install multiple versions of the Intel IPP 7.0 library on your development system, these instructions may be useful to you.

If you have not yet installed a copy of the 7.0 Intel IPP library on your development system please read How to Install the Intel IPP 7.0 Library on Windows.

With release 7.0 of the Intel IPP library the location and layout of the Intel IPP library files on your development system were changed. Rather than being installed as a standalone product within the "\Program Files\Intel\IPP" directory, the Intel IPP library files are now installed as part of the Intel Composer XE product. This was done to provide closer integration with Microsoft Visual Studio, the Intel C/C++ Compiler and other Intel performance library products (such as Intel MKL and Intel TBB).

The following screen shots are the result of installing Intel IPP 7.0.4 on a Microsoft Windows 64 Server 2008 system that had a prior installation of Intel IPP version 7.0.3 already in place (or an Intel Composer XE, Intel Parallel Studio XE or any other Intel Tool Suite for Windows product that contains the Intel IPP library). The details may vary depending on the specific version of the 7.0 library product (either standalone or as part of a tool suite) you already have installed on your development system – these instructions assume a previous version of the Intel IPP 7.0 standalone library product has already been installed on the target system.

Note: if you have only pre-7.0 versions of the Intel IPP library installed on your system (e.g., version 6.1, 5.3, etc.) the following instructions do not apply; you can consider your initial installation of the 7.0 library to be a "clean install" of the Intel IPP library and should review How to Install the Intel IPP 7.0 Library on Windows.

Not every step in the process is shown below, only those steps that are considered of significance are provided.

Upgrade vs. Side-by-Side Installation

If you already have a 7.0 version of the Intel IPP library installed on your Windows development system, after you start the installer and answer any questions about extracting and licensing, you will see a dialog box similar to that shown below.

Choose the SECOND OPTION in the dialog box below (I want to install this update separate [sic] from the existing version).

If you choose the first option (I want to apply this update to the existing version) shown above you will upgrade your copy of the Intel IPP library. This means that the previous version of the library will be overwritten with the version you are now installing.

Choosing the second option (I want to install this update separate [sic] from the existing version) means you want to perform a side-by-side installation of the Intel IPP library. In other words, the existing copy of the Intel IPP library, that is already installed on your system, will remain in place and a second copy will be installed in a new location on your development system.

Obviously, you cannot build an application using both copies of the library at the same time, your build scripts (makefiles) and/or project files will need to be adjusted to specify which copy of the library you should be linking against ("default" or "side-by-side").

Complete the Side-by-Side Installation

Choose "Custom Installation" in order to see the screens that follow.

Notice the name of the directory into which the Intel IPP library components will be installed. In a "default" installation the .x.yyy part of the directory name (.4.196 in this example) would not be part of the directory name.

The convention followed by the installer and the Visual Studio integration tools is that the "unadorned" install directory (the directory with just "ComposerXE-2011" in the name) is the "default" installation directory. Files stored here are the "default" files and will be overwritten if an upgrade installation was chosen.

Any directory that includes a name that has been "adorned" by version-specific details (such as "ComposerXE-2011.4.196" as shown below) is considered to be an optional "side-by-side" directory and will not be overwritten by any future upgrade installs.

Be sure the components you wish to install on your development system include a green '+' sign, as shown below.

The test system used to obtain these screen shots did not have Microsoft Visual Studio installed. That is why the Visual Studio integration steps are grayed out in the following dialog box.

On a Windows 64 system the Intel IPP library (and other Intel Composer XE components) will be installed in the "\Program Files (x86)\Intel\…" directory, regardless of whether you are installing the 32-bit or the 64-bit version of the Intel IPP library. On a 32-bit Windows system the installer will place files in the "\Program Files\Intel\…" directory.

Following a successful installation it is important to note that the Windows "Start Menu" does not contain an "Intel IPP Library" product shortcut. Instead, you will find Intel IPP product documentation and other shortcuts under the "Intel Parallel Studio XE 2011" program group, as indicated by the closing installation dialog box shown below (Intel IPP is a component of Intel Composer, which is a component of Intel Parallel Studio).

Using Windows File Explorer, you can see that the The Intel IPP 7.0 library "side-by-side" binaries are located within the "adorned" Intel Composer XE 2011 directory (see the image below). Notice that the original "default" installation is still present on the development system and is identified by the "unadorned" Intel Composer XE 2011 directory.

Unlike prior versions of the product, the Intel IPP library files are no longer located in a dedicated directory structure. This will impact how you specify your IPPROOT environment variable, if you use this mechanism to locate the library within your project files or build scripts, and where you will find any shared library components (such as the Intel OpenMP library files and the Intel Compiler C runtime library files) that your application might require.