-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
fix nix environment #1294
fix nix environment #1294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested the pr and i was able to use nix develop
I was testing this and I fixed it with this commit |
@buurro that's because we are mixing installing software with nix and non-nix mechanisms. Ideally we'd installing everything with nix and then this wouldn't be a problem. However, as this is a learning tool mixing mechanisms might be ok, it depends a bit on the goal maintainers had when introducing nix here. Would be nice to hear from a maintainer to know what they think. |
Not sure what exactly the problem is here, but if you want my rationale, I merged the original PR so that people with Nix installed could just run If this PR fixes the flake for people that've had trouble working with this, though, then I'd be inclined to merge it. |
Thanks for the clarification, so there are two main problems currently with the nix setup:
This PR fixes both issues. As this is simply about having an easy to deploy environment I think we can forget about the nix way and install everything that is required to build rust applications using cargo so I just pushed another commit to add the required dependencies on macos. I also added |
Since I can test this on Darwin, and main is indeed broken, and this fixes it, that's good enough for me to merge. Thanks! |
@all-contributors please add @dbarrosop for infra |
@diannasoreil I've put up a pull request to add @dbarrosop! 🎉 |
In addition to the issue described in #1292 it also sets correctly RUST_SRC_PATH and patches
rustlings lsp
to make use of it if available. Otherwise the path forsysroot_src
is computed wrongly makingrust-analyzer
fail.