-
Notifications
You must be signed in to change notification settings - Fork 349
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
Need to fix 'miri' bash script for Windows powershell users #978
Comments
Unfortunately I have no experience with bash scripts on Windows, nor with PowerShell. But I'd happily review a PR trying to fix this. :) I am surprised the bash script does anything on Windows. I didn't even know PowerShell can run bash... |
@JOE1994 so now that this works, do you think we could somehow use the |
@RalfJung I currently have zero knowledge of AppVeyor CI. I'll need some time to learn about it before I can say something about it 😢 Lines 1 to 6 in 0d01c30
Is the AppVeyor script solely for Windows ?? |
Yes AppVeyor is for Windows only. So really the main question is: how do I get bash onto Windows? Is that a normal thing for Rust devs to do on Windows?
|
In either Powershell or the Batch shell (2 shells that come with Windows), it is possible to run bash scripts or enter bash shell by using the
Maybe I should ask this question to the Rust language forum or the Rust subreddit to find out.. https://users.rust-lang.org/t/is-it-normal-to-use-bash-on-windows-to-build-rust-projects/33628 |
Hm, but |
Oh.. I just realized that |
That still seems to be rather experimental on the AppVeyor side: appveyor/ci#1295. So, probably best to stick to our current scheme for now. Thanks for testing the script on WSL though, good to know it works now! |
Git for Windows ships with bash ( |
While trying to work on Issue #707 locally, I got stuck with 'Testing the Miri driver' step. I used Powershell to confront the above error. The current issue is that $MIRI_SYSROOT fed to the miri executable is stripped off of its backslashes, resulting in an error "can't find crate for std"
Maybe the 'miri' bash script should be fixed to escape backslashes for windows users?
Or it could also be an issue with cargo
The text was updated successfully, but these errors were encountered: