-
Notifications
You must be signed in to change notification settings - Fork 29
crypto_box: select x25519-dalek
backend automatically
#55
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
crypto_box: select x25519-dalek
backend automatically
#55
Conversation
Introspects the target pointer width to automatically select either the `u32_backend` or `u64_backend`. If the backend isn't 32/64-bit, generate a compile error with an informative message. Removes the explicit `u32_backend`/`u64_backend` crate features in `cargo_box` itself. Now `--all-features` works.
Introspects the target pointer width to automatically select either the `u32_backend` or `u64_backend`, similar to #55. If the backend isn't 32/64-bit, generate a compile error with an informative message.
Introspects the target pointer width to automatically select either the `u32_backend` or `u64_backend`, similar to #55. If the backend isn't 32/64-bit, generate a compile error with an informative message.
Does this work when crypto_box is used as dependency (just adding |
I can also reproduce this, but I haven’t had a chance to fully debug what is going on. |
Sorry to hear this is causing issues. I can revert it. It would be great to get some more information about the error you're encountering though. I can see how it might be an issue on 32-bit platforms, since FWIW, it builds on two 32-bit targets in CI. And I just pushed up a PR that adds full |
Here's the errors: https://github.com/trevyn/sealed_box/runs/7829889187
|
Yeah, that looks like two backends were activated at the same time. Is there not another dependency that uses Regardless I guess this doesn't work because other dependencies may activate a different backend so fine-grained control is needed to match. |
Yes, the only dependency I add is
So it's not the case :) |
It seems it wasn't supposed to work in cargo: rust-lang/cargo#10053 |
PR to revert these changes here: #63 |
|
Introspects the target pointer width to automatically select either the
u32_backend
oru64_backend
.If the backend isn't 32/64-bit, generate a compile error with an informative message.
Removes the explicit
u32_backend
/u64_backend
crate features incargo_box
itself. Now--all-features
works.