Closed FrozenDroid closed 11 months ago
[patch.crates-io]
async-io = { git = "https://github.com/smol-rs/async-io.git", rev = "d9c9ed8" }
socket2 = { git = "https://github.com/rust-lang/socket2", rev = "77e3bb9" }
seems to fix my issue - I suppose we need to wait for async-io and socket2 to release new versions to fix this.
Upstream support for ESP IDF in the smol
ecosystem is in an odd shape right now:
We need new releases for the following crates, as the ESP IDF changes are upstreamed in there, but not released yet:
socket2
polling
rust-errno
Crates where the ESP IDF changes are upstreamed and also released:
rustix
Crates where ESP IDF changes are upstreamed, yet their master
branch is not usable yet:
async-io
, because of thisIn the meantime, what you can do is:
async-io
to an old version as done here and herepolling
and socket2
(and possibly, the smol
aggregation crate itself) as done here to earlier not upstreamed forks. also done here UPDATE:
Crates which still need a small PR to be upstreamed:
smol
, here. No big deal as smol
is just an aggregator crate anyway.@FrozenDroid Small progress update:
polling
3.0 was released recently, with all ESP-IDF-related changes upstreamedrustix
,socket2
and errno
are also upstreamed and released. Waiting for the release of async-io
2.0 now, which I hope is imminent, and which would probably be released together with smol
2.0.
That would complete the upstreaming story of ESP-IDF in the smol-rs
echosystem.
Quite easy to reproduce - just build master and you will see many errors involving libc.