Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Windows] CMake preset llm-debug-vulkan selects MSVC instead of Clang, causing XNNPACK compilation failures

已关闭
  • 哪里不对？
#22,084 1 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@SS-JIA 已经在做这个了。

开始于 2026年8月24日。

  • #22163 来自 @SS-JIA —— 未关闭

评估

这个 Issue 还没有评估数据。

描述

module: vulkan module: windows module: xnnpack triaged
🐛 Describe the bug

When compiling the parakeet-vulkan target using make parakeet-vulkan I am getting a compilation error during XNNPack compilation:

  (compiling source file '../../../../../backends/xnnpack/third-party/XNNPACK/src/subgraph.c')

C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(2663,3): error C2143: syntax error: missing ')' before 'string' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]
C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(2663,3): error C2059: syntax error: ')' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]
C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(2918,5): error C2143: syntax error: missing ')' before 'string' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]
C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(2918,5): error C2059: syntax error: ')' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]
C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(3500,5): error C2143: syntax error: missing ')' before 'string' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]
C:\git\executorch\backends\xnnpack\third-party\XNNPACK\src\subgraph.c(3500,5): error C2059: syntax error: ')' [C:\git\executorch\cmake-out\backends\xnnpack\third-party\XNNPACK\xnnpack-subgraph.vcxproj]

Looking at the first lines of the make output it looks like make is using my installed msvc compiler instead of my installed clang compiler which then fails to compile XNNPACK.

D:\git\executorch>make parakeet-vulkan
"==> Building and installing ExecuTorch with Vulkan..."
cmake --workflow --preset llm-debug-vulkan
Executing workflow step 1 of 2: configure preset "llm-debug-vulkan"

-- Building for: Visual Studio 18 2026
-- Selecting Windows SDK version 10.0.26100.0 to target Windows 10.0.26200.
-- The C compiler identification is MSVC 19.51.36256.0
-- The CXX compiler identification is MSVC 19.51.36256.0
-- Detecting C compiler ABI info                                                 -- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/18/Professional/VC/Tools/MSVC/14.51.36231/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/18/Professional/VC/Tools/MSVC/14.51.36231/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- ExecuTorch version: 1.5.0

Is this expected behavior or this is a configuration issue?

My local Visual Studio environment has Clang installed, yet it is not being found by the collect_env.py script. Ideally Windows this Clang version would be detected to give developers a better experience

Image
Versions

c:\git\executorch>python collect_env.py
Collecting environment information...
PyTorch version: 2.13.0+cpu
Is debug build: False
CUDA used to build PyTorch: Could not collect
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Enterprise (10.0.26200 64-bit)
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 4.4.1
Libc version: N/A

cc @SS-JIA @manuelcandales @digantdesai @cbilgin @GregoryComer @JakeStevens

主要语言
Python
星标
5.1k
派生
1.2k
平均合并
2 天 51 分钟
30 天内合并 PR
712

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pytorch/executorch 的其他 Issue

查看 pytorch/executorch 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。