ifortvars.bat not setting PATH to ifort.exe binary

Dear all,

I have been trying to achieve the same as Simon in https://software.intel.com/en-us/forums/topic/294900, with following setup:

This is on a Windows Server 2012 using Visual Studio 2013 and Visual Fortran 15.0. More precisely

Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.51209

together with

Intel(R) Visual Fortran Compiler XE 15.0 Update 1 for Windows*
Intel(R) Debugger Extension 7.7-8.0 for Intel(R) Many Integrated Core Architecture

Like Simon, we use ifortvars.bat on an older machine, and I can then run cl, nmake and link to build a cross-language DLL.

I found ifortvars.bat and according to its documentation, should run it with arguments "intel64 vs2013", and while this does set some paths (like Simon, I compared the output of set before and afterwards), it fails to set the path to the actual ifort.exe binary, and to the SDK tools such as cl, nmake and link.

The documentation (locally at C:/Program Files (x86)/Intel/Composer XE 2015/Documentation/en_US/beginusing_wf.htm) says to use the Command prompt with Intel Compilers, (supposedly found at Start > All Programs > Intel Parallel Studio XE 2015 > Compiler and Performance Libraries), but this is not installed on our machine - said start menu path only contains a link "Use VS2013", so I do not have an example to use as reference.

Also, the docs concerncing using the command-line say

The Intel® Fortran Compiler includes a shell script that you can run to set environment variables.

• On Linux* and OS X*, the file is a shell script called compilervars.sh or compilervars.csh.
• On Windows*, the file is a batch file called compilervars.bat.

but this seems to be specific to the Intel C/C++ compiler; there is no such script on this machine.

I guess I could hack this, using the SDK vcvarsall.bat script and hardcode %INTEL_COMPILER15%bin\intel64\ifort.exe (or similar), but I would very much like to keep our build scripts clean and less dependent on particular installation paths.

I am attaching our ifortvars.bat (as txt) and the (slightly redacted) before and after outputs of SET.

Thank you for your consideration!