This repository has been archived by the owner on Jan 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
Depend on a no_std compatible version of chrono #60
Comments
I'd like to note that crates.io doesn't accept crates that depend on git repositories, so switching to chrono's GitHub version would effectively block new versions of cortex-m-rt from being released. |
...Oh, I definitely didn't realize that, yeah, that's definitely not worth it! |
https://crates.io/crates/chrono is now at 0.4.1 which is no_std compatible. \o/? |
japaric
added a commit
that referenced
this issue
Apr 6, 2018
Minor version has been bumped to v0.4.0 so we can stop supporting them This also drop the chrono dependency, which some people have been running into problems with. closes #60
Note that because of rust-lang/cargo#4866 it is not enough for chrono to support |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm running into a dependency conflict where I can't depend on
uom
because it depends onnum-traits
, which has been made no_std compatible since the most recent version ofchrono
. The problem is, the released version ofchrono
depends on a conflicting version ofnum-traits
that requiresstd
. Why cargo can't sort out conflicts of this sort is beyond me, but since it can't, wouldcortex-m-rt
switching to the github version ofchrono
be permissible (at least untilchrono
gets their act together and cuts a no_std compatible release)?To recreate the problem for yourself, all you have to do is start a blank no_std library project, add a dep for
verify that xargo can build it, then add a dep for
cortex-m-rt = "*"
and try to build againThe text was updated successfully, but these errors were encountered: