VS Code: Generate launch configuration
does not respect RUSTUP_HOME
correctly
#18468
Labels
C-bug
Category: bug
rust-analyzer version: 0.3.2162-standalone (3b3a87f 2024-10-27) (VS Code extension bundled)
rustc version: 1.82.0 (f6e511eec 2024-10-15)
editor or extension: VS Code, extension v0.3.2162
platform: Windows 10
relevant settings: (eg. client settings, or environment variables like
CARGO
,RUSTC
,RUSTUP_HOME
orCARGO_HOME
)CARGO_HOME
:E:\.dots\.cargo
RUSTUP_HOME
:E:\.dots\.rustup
Using the
Generate launch configuration
command in VS Code fails with the following output:As best as I can tell,
RUSTUP_HOME
is being ignored, and it instead uses the default per-user location ofC:\Users\<user>\.rustup
. Deleting the per-user folder and running the command again will re-generate the folder, with a defaultsettings.toml
which contains only the following:Copy-pasting the contents of the
settings.toml
in myRUSTUP_HOME
into this one makes it work, but it then installs an independent Cargo into my user folder and re-fetches dependencies to there, which is not ideal, as I moved the directory to a secondary drive due to the limited space on my primary drive.The text was updated successfully, but these errors were encountered: