System: Windows Server 2022 Standard
Visual studio: 2019
OneAPI: 2025.2.1.46
It seems that xilink.exe, when given normal windows paths passes paths with slashes instead of backslashes to link.exe. Normally this works, but if a path starts with a slash, e.g. a network path, link.exe interprets it as an option. Very simple example:
C:\Users\ulfw\Projects\mosek\master>xilink \\files\public\windows\intel\oneAPI-2025.2.0\mkl\2025.2\lib\mkl_core.lib
xilink: warning #10047: Tool use is limited for IL0 based targets. Please use the IL0 based build.
xilink: executing 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\link.exe'
Microsoft (R) Incremental Linker Version 14.29.30157.0
Copyright (C) Microsoft Corporation. All rights reserved.
//files/public/windows/intel/oneAPI-2025.2.0/mkl/2025.2/lib/mkl_core.lib
LINK : warning LNK4044: unrecognized option '//files/public/windows/intel/oneAPI-2025.2.0/mkl/2025.2/lib/mkl_core.lib'; ignored
LINK : warning LNK4001: no object files specified; libraries used
LINK : warning LNK4068: /MACHINE not specified; defaulting to X64
LINK : fatal error LNK1561: entry point must be defined
Basically, this affects any library or object located at a network location or if an absolute path is given without drive (e.g. "\users\someone\somefile.obj").
I should mention the previous versions of oneAPI correctly used backslashes.
Is there a way around this?
