-
Notifications
You must be signed in to change notification settings - Fork 227
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
no_std fails to build #95
Comments
You may be running into rust-lang/cargo#5730 |
I have no build-dependencies in my minimal example. Only this:
..and dropping the |
What does your Cargo.lock look like? |
|
just in case this helps:
|
|
cc @hdevalence |
The interaction seems to be complex, because curve25519-dalek builds fine with |
I think I made it work by removing dev-deps and adding two default-features=false in my fork of ed25519-dalek: test it with: |
Hi! I similarly suspect you're running into the cargo build-dependencies features issue. However, you'll also want to ensure you're using |
I think rand_os activates std before 0.2.1, so before rand 0.7. As rand_core 0.4 alone works, your library crate could pass its own tests no_std, but break no_std inside application: w3f/schnorrkel#31 (comment) |
Hi @brenzi! Are you still running into this issue? If so, please feel free to reopen (I'm trying to triage out old bugs that are no longer relevant). |
Reproduce:
build the following minimal crate:
https://github.com/scs/test-no-std/tree/ed25519-dalek
cargo build --no-default-features
results inThe text was updated successfully, but these errors were encountered: