-
Notifications
You must be signed in to change notification settings - Fork 83
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 compilation #62
Comments
Hmm this is probably a failure of our CI to catch this. I see yasna went from an optional dependency to a required dependency a few weeks ago in 186268c. @jack-fortanix any comment? Dev dependencies should be compiled for your host, so I'm not sure what's going on there. |
Firstly, I'm not sure how chrono is getting pulled in, as the only feature enabled is core_io. Secondly I think I am running into the cargo issue I linked in my first post, byte-order is pulled in by |
Re yasna, we need the extensions parsing internally, but could gate use of yasna behind |
64: Make yasna optional again as it does not support no-std builds r=jethrogb a=jack-fortanix See #62 Co-authored-by: Jack Lloyd <[email protected]>
65: Only require chrono when we actually use it r=jethrogb a=jack-fortanix See #62 Co-authored-by: Jack Lloyd <[email protected]>
With |
I'm having alot of trouble building this crate on a truly no_std platform (thumbv7m).
Initial findings are that
yasna
uses std, but beyond that there seems to be a whole heap of other issues like dev dependencies attempting to build and failing for that target (which I think it actually a cargo issue).Edit: Looks like its mainly a cargo issue rust-lang/cargo#5730.
The text was updated successfully, but these errors were encountered: