Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix issue with bitflags version dependency in main Cargo.toml
- Loading branch information
Showing
1 changed file
with
5 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8ba0f3e
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.
There is also bitflags-core now!
8ba0f3e
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.
Thanks, I switched to that crate in a8dca8b.
I'd like to change my build process so that I'm getting
libcore
from your phil-opp/nightly-libcore repo rather than from emk/rust@e064738, so that my build process is no longer tied to a specific Rust nightly build and I can build against the latest Rust nightlies; I just haven't gotten around to it yet.8ba0f3e
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.
Awesome, let me know how it works out!
8ba0f3e
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.
I just learned that the official bitflags has a
no_std
feature now: bitflags/bitflags#298ba0f3e
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.
Good to know! It looks like the official bitflag crate is up-to-date with the current nightly though, and thus doesn't enable the
no_std
feature gate. Right now it won't work for me yet 'cause my build process is still locked in to an older version of Rust.I'm actually having some problems switching over to your
nightly-libcore
crate, but I'll open an issue for them on your repo for the crate.8ba0f3e
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.
Okay, I opened an issue (phil-opp/nightly-libcore#3) for the problem I'm having with your version of
libcore
. Any time you can check it out, I'd really appreciate that. No rush, of course.