For Eclipse Managed Make Projects, you can select different versions of the Intel compiler (the two most recently released major versions) to compile your Eclipse Intel project. Eclipse configurations are used to provide this support. You select which version of the Intel compiler that you would like to build your project with through selection of the configuration associated with the desired version of the compiler prior to building your project. You can create the desired configurations for the versions of the compiler that you would like to build either when you create an Intel project, initially, or through the Manage Configurations interface within the IDE, accessible via the project’s properties (Right click the project, select Properties->C/C++ Build, then select the Manage... button on the line entitled Configurations and then New). Within configurations, you can set distinct project properties, like compiler options, to be used with different versions of the Intel compiler and freely select and modify which version of the compiler with which to build by changing the active configuration, i.e. the configuration that is in effect when your application is built within the Eclipse IDE.
Note that if you have multiple instances of the same major version of the compiler installed on your system (and, for an Eclipse Managed Make Project, a configuration with that major version is active) with different minor versions, the Eclipse IDE will, by default, use the compiler with its environment established, via execution of <install-dir>/bin/iccvars.*sh. If no compiler environment is established for an Eclipse/CDT Managed Make Project, then the most current compiler, i.e. the one with the highest minor version number, will be used by default. For an Eclipse/CDT Standard Make Project, the compiler environment must be established to enable successful invocation of the compiler, by default. Note also, that for both Managed Make and Standard Make projects, the compiler environment can be set by the user through specification within Eclipse, and that this compiler specification will override any specification established outside of Eclipse.