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.