You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UEFI app tutorial at https://rust-osdev.github.io/uefi-rs/HEAD/tutorial/app.html does not work with the current version of the uefi crate available from crates.io.
The book refers to the latest state of the source repo, and not what is published on creates.io, although it instructs to use cargo add uefi to add the crate.
The current crates.io version (0.27.0) does not have the uefi::helpers mod yet, and thus stuff does not build -- very confusing.
Maybe the Rust book needs to be versioned?
Or only rebuild it when the create is published to crates.io?
Yes, the README.md at the uefi-v0.27.0 tag points to a working example, but the documentation linked at crates.io also points to the Rust book, following HEAD instead of pointing to the correct version.
The text was updated successfully, but these errors were encountered:
We made that API change very recently. We should publish the new crate versions ASAP, @nicholasbishop . Then these kinds of problems will no longer occur, when people use the latest crates.
The UEFI app tutorial at https://rust-osdev.github.io/uefi-rs/HEAD/tutorial/app.html does not work with the current version of the uefi crate available from crates.io.
The book refers to the latest state of the source repo, and not what is published on creates.io, although it instructs to use
cargo add uefi
to add the crate.The current crates.io version (0.27.0) does not have the
uefi::helpers
mod yet, and thus stuff does not build -- very confusing.Maybe the Rust book needs to be versioned?
Or only rebuild it when the create is published to crates.io?
Yes, the README.md at the uefi-v0.27.0 tag points to a working example, but the documentation linked at crates.io also points to the Rust book, following HEAD instead of pointing to the correct version.
The text was updated successfully, but these errors were encountered: