[CMake] CMake problem with intel parallel studio 2017

[Mamales, Petros]

Hi Brad,
Thank you for the one-to-one answers! Much appreciated!
I was afraid of 3) as a reasonable answer. Unfortunately intel PSXE installation process has some desirables as a process, and 
things do not always work as intended, hence I was hoping for a workaround.
In case  you would like to oblige even more: how is the specification of the toolset (from command line) translates to the modules folder in CMake?
(only if it is not too much to ask).
At any rate, thank you very much again and have a very nice weekend!
Petros

-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com] 
Sent: Friday, June 09, 2017 11:01 AM
To: Mamales, Petros [CCC-OT NE]
Cc: CMake
Subject: Re: [CMake] CMake problem with intel parallel studio 2017

On 06/08/2017 03:02 PM, Mamales, Petros  via CMake wrote:
> I try to create Visual Studio 2015 (VS2015) solutions with the intel 
> c++ compiler from Intel Parallel Studio XE (iPSXE) 2017.
> a)      How does the identification of the toolset proceed? (I used the -T command line option)

It works for me like this:

    >cmake --version
    cmake version 3.9.0-rc2

    >cmake ..\src -G "Visual Studio 14 2015" -A x64 -T "Intel C++ Compiler 17.0"
    -- The C compiler identification is Intel 17.0.0.20160721
    -- Check for working C compiler: C:/Program Files (x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe
    -- Check for working C compiler: C:/Program Files (x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe -- works

This does *not* need to be run at a command prompt with any special environment for the compiler.

> 1)      How are these tests really run?

It generates a .vcxproj file with the PlatformToolset field set and then runs MSBuild.

> 2)      How is the toolset endowed with the necessary include and link/lib directories (within CMake).

MSBuild takes care of this when running the compiler inside its environment.

> 3)      How can I append more of these directories to "help" the compiler identification and/or attributes discovery?

You shouldn't need to do this, and there isn't really a way to do it.

-Brad