From 1914a42b1c4cf6203ed3e33efe5e64a74c3b404c Mon Sep 17 00:00:00 2001 From: IceSentry Date: Mon, 10 Jun 2024 17:51:30 -0400 Subject: [PATCH] Update windows doc to mention rust-lld linker error (#12859) Release Notes: - N/A ## Description When using rust-lld it's possible to get a `STATUS_ACCESS_VIOLATION` error at compile time. I added a bit of information about it in the build guide for windows to recommend using a different linker when building `zed`. --------- Co-authored-by: Marshall Bowers --- docs/src/development/windows.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/src/development/windows.md b/docs/src/development/windows.md index 190338e3ff..b9c0dd2477 100644 --- a/docs/src/development/windows.md +++ b/docs/src/development/windows.md @@ -86,3 +86,11 @@ Before reporting the issue, make sure that you have the latest rustc version wit ### Cargo errors claiming that a dependency is using unstable features Try `cargo clean` and `cargo build`. + +### `STATUS_ACCESS_VIOLATION` + +This error can happen if you are using the "rust-lld.exe" linker. Consider trying a different linker. + +If you are using a global config, consider moving the Zed repository to a nested directory and add a `.cargo/config.toml` with a custom linker config in the parent directory. + +See this issue for more information [#12041](https://github.com/zed-industries/zed/issues/12041)