Toolchain is reportedly not installed, even though it very much is #89
Comments
ide-rust uses the path that the atom process is supplied with & also adds You could have a different environment setup launching atom & executing on the cli. On windows env var changes sometimes only take effect after logging-out & in again, so that's worth a try if you've changed env vars in your current session. It sort of looks like you have 2 different rustup installs, that ide-rust's rls could think a toolchain wasn't installed that the cli does. Is that possible? It might be worth me adding PATH info to the error logging to help debug these kind of issues. |
Hmm, I don't think I've installed
I haven't tried relogging yet, I'll do it when I can. |
Unfortunately relogging didn't help; any other options/debugging I can try? |
Well I guess you can look at the env vars supplied to atom by typing into the console:
Maybe theres a difference from when you run |
I ran |
The case should be fine I have I actually may have an idea, I remember having some issues in windows when not passing the full env with the commands. ide-rust does that now, but I just noticed only for starting rls rather than the earlier I will add it in both places and make a release. |
Ok I've made the |
That did the trick; thanks! |
I'm getting errors pointing to a missing
rustup
installation while I'm very certain it is available and present inPATH
:Running
rustup run stable-x86_64-pc-windows-gnu rustc --version
incmd
works nicely and returnsrustc 1.27.0 (3eda71b00 2018-06-19)
.rustup component list --toolchain stable
confirms that the required components are there:I've also tried to make it work with
nightly-x86_64-pc-windows-gnu
(that I also have along with RLS), but it only changed the flavor of the error to:Debug mode doesn't show any more errors.
The text was updated successfully, but these errors were encountered: