-
Notifications
You must be signed in to change notification settings - Fork 20
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 not compiling #51
Comments
Hey sorry for the slow reply, does PR #53 resolve you issue such that it will now compile without |
No, that PR did not actually solve the issue. The command Related comments: Line 13 in d3fc0a4
There, it points to https://github.com/sigp/incubator-milagro-crypto-rust/tree/057d238936c0cbbe3a59dfae6f2405db1090f474 In that repo, we see the package amcl ’s lib.rs file: https://github.com/sigp/incubator-milagro-crypto-rust/blob/057d238936c0cbbe3a59dfae6f2405db1090f474/src/lib.rs So, what I did to try forcing a no_std environment was clone the amcl crate above, and add #![no_std] to the lib.rs and see if it would compile. It did not compile. |
@tbraun96 good point! @kirk-baird I think supporting no-std is actually a little more involved than PR #53 accomplished. Essentially a clean way to do it is so like this: Declare imports: https://github.com/serde-rs/serde/blob/master/serde/src/lib.rs#L151 So you toggle between I attempted this for the |
I am trying to use this crate with the Substrate framework, which requires the
no-std
feature. It looks like this crate supports running in no-std environments, if I look atCargo.toml
. However, when I try to compile the crate I get the following compiler errors:I will try to fix these in a forked version, but just wanted to get your input in case I might be missing something.
Is the crate only supported for nightly builds?
The text was updated successfully, but these errors were encountered: