-
Notifications
You must be signed in to change notification settings - Fork 2
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
build requires nightly due to exit_status_error
#1
Comments
Indeed, this does currently require nightly compiler. AFAIK this feature is on it's way to be stabilized so this requirement should disappear eventually. If I understood @Qyriad correctly it should be possible to work around this and not need nightly. But I am not sure about the details. |
Correct. All the instances of let success = cmd
.status()
.unwrap()
.success();
if !success {
panic!("msg_here");
} Iirc at the time the Windows build required nightly anyway, but I think that's no longer the case. |
Thank you very much for the clarification @Qyriad :) @xobs there are two ways we can approach it. We either change the code to remove the nightly requirement for now, but then we will probably not even notice when the feature becomes stable. Or we can leave it and just keep using the nightly for now. I did not make my mind up yet which solution is a better one. I could subscribe to the issue on rust-lang that you provided and monitor it. And keep a tracking issue for us to clean up the code eventually when the nightly feature becomes stable. What are your suggestions and preferences? |
I don't know when Rust will stabilize that feature. They tend to take a very long time, so it could be months. Meanwhile, it's a relatively simple patch, and I can confirm that #2 builds just fine on Rust 1.65.0. Unless there's a reason to keep the nightly requirement for this feature -- for example ensuring that beginner developers don't build this themselves -- then I don't see the benefits of requiring nightly. |
We're looking to tagging v0.1.0 so we can run a publication cycle to crates.io, as you've not posted anything further, may we assume that things have been working well for you and we can close this xobs? |
Things have indeed been working well! Thanks for the discussion and the fixes. |
This library requires a nightly build, due to
build.rs
using#[feature(exit_status_error)]
. This is part of issue rust-lang/rust#84908.It is possible to build this using a stable compiler by setting
RUSTC_BOOTSTRAP=1
or by using a nightly compiler.The nightly requirement should be noted in the
README
, or this feature should be removed to allow it to be built on a stable compiler.The text was updated successfully, but these errors were encountered: