-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Cannot set rustcSource to rustc-dev rustup package #7589
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I think you need to point to |
|
There's no such file:
|
Maybe try the |
I would assume you need an actual checkout of rustc. |
That would be rather unpractical -- the crates it is linking against are installed via rustup, so to make sure the source matches, that should also be taken from rustup. The |
No that does not work either:
|
I've found what the root cause of this particular issue is: the |
Since it was missing, it wasn't possible to really use rustc-dev to build, see for instance: rust-lang/rust-analyzer#7589.
…=Mark-Simulacrum dist: include src/build_helper as part of the crate graph for rustc-dev The build_helper dependency is used to build the compiler/rustc_llvm build script. Since it was missing, it wasn't possible to really use rustc-dev to build, see for instance: rust-lang/rust-analyzer#7589.
…=Mark-Simulacrum dist: include src/build_helper as part of the crate graph for rustc-dev The build_helper dependency is used to build the compiler/rustc_llvm build script. Since it was missing, it wasn't possible to really use rustc-dev to build, see for instance: rust-lang/rust-analyzer#7589.
@bnjbvr can this be closed now? |
With the latest rustc, pointing to However, it seems rather strange that I would have to pick one of the many compiler crates. Why rustc_driver? At the very least, the docstring for |
Pointing it to |
We are setting |
In an attempt to get rust-analyzer to work better for working on Miri (which imports rustc-private crates), I tried setting
rust-analyzer.rustcSource
to/home/r/.rustup/toolchains/miri/lib/rustlib/rustc-src/rust/compiler/
, where therustc-dev
rustup package puts the sources. However, that does not work -- I am getting an error saying "the manifest path must be a path to a Cargo.toml file".Is there any way to make rust-analyzer use the sources included in the rustc-dev package?
The text was updated successfully, but these errors were encountered: