Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode + RLS install is a mess #1301

Closed
freedaun opened this issue Dec 5, 2017 · 8 comments
Closed

VSCode + RLS install is a mess #1301

freedaun opened this issue Dec 5, 2017 · 8 comments

Comments

@freedaun
Copy link

freedaun commented Dec 5, 2017

  1. I have a fresh Windows 10. FRESH.
  2. Installed VSCode, so rustup will know it can do its integration thing.
  3. I installed Rust with Rustup, which prompted me to install the MS C++ Build Tools, so before continuing I:
  4. downloaded and installed 5.6GB worth of C++ Build tools. Says it Installed. But I have to take its word for it? :(
  5. Aborted and reran Rustup and installed Rust, per default.
  6. Entered VSCode and opened a Rust project. Nothing happened ;) Isn't RLS is supposedly installed by default per recent release notes??
  7. Typed Rust in VSCode extensions and found Rust 0.4.2. Installed it. Supposedly it features RLS integration. But nothing confirms that.
  8. Installed Rust (rls). VSCode begins talking to me, offering to install RLS.
  9. It requires nightly. Please do install. Many messages and confirmations (do whatever you think you need) and RLS is NOT installed as the end-result.

OBS: I don't see the usual C++ debug profile, nor the dialog prompting me to select

WTF?

I think all of this amounts to the same thing, see title. Sorry.

@sbwtw
Copy link

sbwtw commented Dec 6, 2017

Same problem, I have update nightly toolchain to nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.24.0-nightly (cfba0d446 2017-12-05) and NO rls or rls-preview in component list

@McGittyHub
Copy link

Same it just disappeared

@dvdplm
Copy link

dvdplm commented Dec 6, 2017

Same for rustfmt-preview. I think there's some kind of upstream problem causing some components to be skipped with the nightly builds. I've been using nightly-2017-12-01 which insofar I know is the last build to include both rls and rustfmt. :/

@alexheretic
Copy link
Member

Releases of additional tools are referenced to be built and included in nightly rust releases. If the additional tool's, ie rls-preview's, latest release does not build with latest nightly-rust that tool will be missing. This is an unfortunate fact of nightly life, Rls is fragile to rustc changes and nightly updates can include changes to the compiler.

The long solution is the stabilization of Rls meaning normal development will take place on stable-rust. Until then we have to handle potential nightly absences of Rls.

  • If your nightly install is missing Rls, try installing a previous one, ie nightly-2017-12-01. The atom plugin will prompt you to do this, and I assume vscode is the same.

  • If you have a working nightly and want to update it's possible to check if the latest nightly has Rls and this should be coming to rustup (see [Feature Request] Warn users of component availability changes #1277).

    Until that's in rustup you can use a script, like:

    #!/usr/bin/env bash
    # Update rust nightly as long as rls is included
    if curl https://static.rust-lang.org/dist/channel-rust-nightly.toml 2>/dev/null | grep -q 'rls-preview' 
    then
      rustup update nightly
    else
      echo 'latest nightly is missing rls' >&2
      exit 1
    fi

@jankeromnes
Copy link

See also rust-lang/rls#611 (comment)

@elliottneilclark
Copy link

This gets even worse if you want to use clippy. I haven't found any nightly that is usable if I want to use clippy, fmt, and rls.

@DanielJoyce
Copy link

Its all still a hot mess even after two years. Why is this so dysfunctional?

@Diggsey
Copy link
Contributor

Diggsey commented May 30, 2018

AFAIK, the only rustup-related issue here was that it would allow you to upgrade to a nightly rustc which was built without the RLS. This has been fixed.

@elliottneilclark
Clippy in general does not work well with rustup because it dynamically links to the compiler DLLs, and that is incompatible with toolchain-switching. The solution here will be to distribute clippy as a compiler component, like the RLS and rustfmt. Until then, clippy will break on every compiler update and will have to be reinstalled.

@DanielJoyce
Please open an issue if you have a specific problem. I know many people, including myself have been using rustup, rust and RLS without issue for some time now.

@Diggsey Diggsey closed this as completed May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants