VS 2022 ignores "" in ifx compiler paths under Win11

[JonasFriedrich]

Hello,

we recently changed from Win10 to Win11 and somehow Visual Studio 2022 cuts the path at the spaces within the standard windows program files paths. The IFX Fortran compiler from the oneAPI is used.

If I check under Extras -> Options -> Intel Compilers and Libraries -> IFX Intel Fortran the executables are

$(VSInstallDir)VC\Tools\MSVC\$(VCToolsVersion)\bin\HostX64\x64;...

and the default options are

/Qlocation,link,"$(VSInstallDir)VC\Tools\MSVC\$(VCToolsVersion)\bin\HostX64\x64"

During building this error comes up:

ifx: command line warning #10161: unrecognized source type 'Files\Microsoft'; object file assumed

ifx: command line warning #10161: unrecognized source type 'Visual'; object file assumed

fpp: fatal: can't fopen file: Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX64\x64\ /Qm64  some filepath

Apperently the path of the exectuables or so is broken at the spaces, but I can not figure out why.

In Win10 and in Win11, the Visual Sutdio files have been created with CMake. As said, in Win10 the settings and paths are the same and it works there.

Does Win11 need any additional flag in CMake for applying the correct path? Or any special syntax to include spaces in file paths?

Does anyone encounter the same?

Thanks in advance,

Jonas

[Daniel_Dopico]

Hi, Jonas. 

I am experiencing exactly the same issue and I opened a ticket on that. I'll let you know if we get a solution. I see that the issue could be related to the resource files that the compiler writes including long routes. For example, in my case:

Build Log

Output

Compiling with Intel® Fortran Compiler 2025.2.1 [Intel(R) 64]... Creating temporary file "RSP1.rsp" with contents [ (options and routes here) ] Creating command line "ifx @"C:\Users\*****\Desktop\MBSLIM\MBSLIM.dir\Debug\RSP1.rsp""

There is something very wrong with the routes in the last versions of the Intel compiler. Before this problem with Windows 11 happened, the visual studio stopped linking the errors with the code, even in windows 10 (double click should take you to the code where the error is triggered). This seemed to be related with long routes or routes with special characters.

[Daniel_Dopico]

I checked Visual Studio community 2019 and the problem remains.

[jimdempseyatthecove]

>>fpp: fatal: can't fopen file: ...Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX64\x64\...

This is a MS Visual Studio folder containing binaries (.dll, .exe, etc...)

Why is fpp trying to open a file located in this folder? (??#include "some file there"??)

or

why are you attempting to compile a source file located there (and with the -fpp option)?

Jim Dempsey 

[Daniel_Dopico]

Hi Jim.

We are not attemping to compile any source there. I think the compiler is messing his own routes.

It is working with windows 10 and Intel fortran 2025 and it is working with intel fortran 2024, even in windows 11.

[runborg]

I have witnessed the same problem with Intel oneAPI 2025.2.1 and VS 2022 17.14.**bleep**

However, we don't have this problem with Intel oneAPI 2025.2.0 and VS 2022 17.10.5

Someone has introduced a regressive bug although I don't know who.

[runborg]

I should add my "working" environment does not use the "temporary RSP1.rsp" files in the build log, but the "broken" environment does.

That may help intel engineers understand where this problem is originating.

[runborg]

It seems the the trigger for using RSP files happens when the command is over 1000 characters long. 

As a temporary workaround, we have moved all of our projects to have much shorter paths to decrease the length of commands passed to ifx from cmake.

I also think this issue may be related to: https://community.intel.com/t5/Intel-Fortran-Compiler/ifx-2025-1-fails-under-Windows-with-a-string-macro-defined/td-p/1678415

[JohnNichols]

You need to get to Windows 11 Insider - latest preview to solve the issue of long paths in Windows.

The simplest solution is to use the DOS Subst function and create say z: drive for the data or programs with you long names. 

[Ron_Green]

If this is the same issue as  https://community.intel.com/t5/Intel-Fortran-Compiler/ifx-2025-1-fails-under-Windows-with-a-string-macro-defined/td-p/1678415  then you can expect a fix with the 2025.3.0 compiler.  It is due to release in late October or early November. 

[JonasFriedrich]

At least for me, that seems to be the same issue. Thanks!