Cargo tries to install windows-gnu even it seems not require.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem
I got this issue when I tried to build zed on Windows. When I run any cargo command under the zed repo, it starts info: syncing channel updates for '1.88-x86_64-pc-windows-gnu'. It's weird since the document requires me to install MSVC and Windows SDK, inferring that it uses MSVC toolchain. So I tries rustup default stable-msvc, then I see:
info: note that the toolchain '1.88-x86_64-pc-windows-gnu' is currently in use (overridden '<zed repo path>\rust-toolchain.toml').
Then I open that rust-toolchain.toml file. It has nothing about windows-gnu, only a windows-msvc target, and now I don't get why it wants to use windows-gnu toolchain.
Steps
- Clone the zed repository.
- Tries to build it on Windows.
Possible Solution(s)
No response
Notes
No response
Version
cargo 1.88.0 (873a06493 2025-05-10)
release: 1.88.0
commit-hash: 873a0649350c486caf67be772828a4f36bb4734c
commit-date: 2025-05-10
host: x86_64-pc-windows-msvc
libgit2: 1.9.0 (sys:0.20.0 vendored)
libcurl: 8.12.1-DEV (sys:0.4.80+curl-8.12.1 vendored ssl:Schannel)
os: Windows 10.0.26100 (Windows 11 Professional) [64-bit]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the Zed repository's rust-toolchain.toml and the documented Windows build steps. Compare rustup's toolchain override selection with the file's windows-msvc target while running the reported cargo commands. Done means the cause of the windows-gnu selection is identified and the appropriate rustup behavior or configuration guidance is clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100