FAQ Intel® Parallel Composer Redistributable Package

 

Q: What can be redistributed in the Intel Parallel Composer?
Q: What is the Intel Parallel Composer redistributable package?
Q: Who will need to install the Intel Parallel Composer redistributable package?
Q: On which OS' can the Intel Parallel Composer redistributable package be installed?
Q: What is required in order to install the redistributable package?
Q: Is the redistributable package for the Intel Parallel Composer the only package needed by your customers?
Q: What are the advantages and disadvantages of using the Intel Parallel Composer redistributable package?
Q: Where will the Intel Parallel Composer redistributable package be installed?
Q: If my application is built using all static libraries, do I need to redistribute anything?
Q: How do I link all libraries statically?
Q: How do I check which DLL files are used by my application?

 

Q: What can be redistributed in the Intel Parallel Composer?

A: Only the files listed in credist.txt can be redistributed. You can find the credist.txt file at "<install-dir>\Composer\Documentation" or default at "C:\Program Files\Intel\Parallel Studio\Composer\Documentation\credist.txt".


Intel's redistributable compiler libraries package may be added to the distributed application package for any end-user application built or partially built with an Intel compiler that is distributed by an Intel customer who holds an Intel Commercial or Academic license for the associated Intel compiler product. The Intel redistributable compiler libraries package may be distributed as a separate non-modified module to the end-users of the distributed application.

Q: What is the Intel Parallel Composer redistributable package?

A: The redistributable package is created for simplifying your application's deployment. It contains all the redistributable files listed in "credist.txt". The package is a .zip file containing an IA-32 and an Intel-64 redistributable package. Each package is self-installable.

 

The redistributable package for the Intel Parallel Composer contains both debug and release of dynamic DLLs and static LIBs. If your application also requires Microsoft* Visual C++ runtime libraries, please be aware that Microsoft's redistributable package does not contain the debug DLLs or static LIBs.

 

Q: Who will need to install the Intel Parallel Composer redistributable package?

A: Only the end users who use applications that are built with the Intel Parallel Composer.

 

Q: On which OS can the Intel Parallel Composer redistributable package be installed?

A: Windows Servero 2008*; Windows Server 2003*; Windows Vista*; Windows XP*

 

Q: What is required in order to install the redistributable package?

A: None.

 

Q: Is the redistributable package for the Intel Parallel Composer the only package needed by your customers?

A: Not necessarily.

It depends on how your application is built and which libraries it references. It is best to check what is required to run your application on a clean system that does not have any development tool or library installed.

 

You may need to redistribute the files from Microsoft* Visual Studio 2005* or 2008*. Microsoft also provides the redistributable package for Visual Studio 2005 and 2008 at following locations:

 

Q: What are the advantages and disadvantages of using the Intel Parallel Composer redistributable package?

A: Advantages:

  • Your application is no longer required to include the redistributable files from the Intel Parallel Composer in the product.
  • Your application's package size will be smaller.

Disadvantages:

  • Because we do not know which libraries are used by your product, the redistributable package contains all the redistributable files.
  • Your user will have to download and install the redistributable package first before using your product.

 

Q: Where will the Intel Parallel Composer redistributable package be installed?

A: The installer of redistributable package will install all the files under <CommonProgramFiles>\Intel\Shared Files\cpp

 

Q: If my application is built using all static libraries, do I need to redistribute anything?

A: No in most cases.

But you should be aware of some default behaviors, e.g. the OpenMP* runtime library. Because we recommend every one to use dynamic OpenMP runtime library, you have to specifically tell the compiler or linker to use the static OpenMP runtime library using "/Qopenmp-link:static".

 

So if you did not specify "/Qopenmp-link:static", you need to distribute the Intel OpenMP compatibility library "libiomp5md.dll".

 

 

Q: How do I link all libraries statically?
A: Under the project's property, make sure to do following:

  • Under C/C++ -> Code Generation -> Runtime Library, select "/MT"
  • If your code uses OpenMP, add "/Qopenmp-link:static" to C/C++ -> Command Line -> Additional Options

 

NOTE: Regarding the static OpenMP runtime library, the goal is to use only one OpenMP runtime library for the whole application, including any third party library.

  • Select the Microsoft Visual Studio property page Linker -> Input, then for the property "Additional Dependencies", add all the static libaries' names.

 

Q: How do I check which DLL files are used by my application?

A: You can use several tools to help identifying the dependent DLLs of your application.

  • Use depends.exe from Microsoft* or Dependency Walker from dependencywalker.com.
    This is a GUI ultility.
  • Use dumpbin.exe from Microsoft. This is a command ultility:
    >> dumpbin /DEPENDENTS myapp.exe

 

* Other names and brands may be claimed as the property of others.
**Intel is not responsible for content of sites outside our intranet.

Copyright (C) 2010, Intel Corporation. All Rights Reserved.

Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.