-
Notifications
You must be signed in to change notification settings - Fork 62
building doesn't work on windows when using wsl as integrated terminal #286
Comments
@tinaun, |
@KalitaAlexey I think you can set
Output from cd c:\Dev\RustProjects\three-rs
rustup run nightly-x86_64-pc-windows-msvc cargo check
devusr@DESKTOP-1482QIG:/mnt/c/Dev/RustProjects/three-rs$ cd c:\Dev\RustProjects\three-rs
bash: cd: c:DevRustProjectsthree-rs: No such file or directory
devusr@DESKTOP-1482QIG:/mnt/c/Dev/RustProjects/three-rs$ rustup run nightly-x86_64-pc-windows-msvc cargo check
rustup: command not found
devusr@DESKTOP-1482QIG:/mnt/c/Dev/RustProjects/three-rs$ |
yeah, thats what ive been doing. in previous versions of the plugin, i could use build tasks to build the windows version and the integrated terminal to build a linux version all from within vscode! very convenient |
I have opened the issue to fulfill what you want. |
@tinaun, |
The extension couldn't do anything about |
I can't use bash.
If I run |
see this vscode issue: microsoft/vscode#6579 (comment) using |
Thanks. I'll try that. |
Everyone who is interested, please look at #315 |
Version of VSCode: 1.13.1
Version of the extension: 0.4.0
OS: Windows 10
when running the cargo build task, it tries to run the commands on the integrated terminal as if it was cmd, using windows style path seperators and looking for a pc-windows-msvc build of rust, both of which error out. previous versions would just run
cargo build
, which worked the same on both terminals.Output of the "Rust logging" channel:
The text was updated successfully, but these errors were encountered: