ivmarkov

> > > While creating an embedded-svc wifi manager I came across some issues which could easily be resolved by expanding the http server traits (the new ones) or adding...

I suggest let's wait here a week or so. I'm in the midst of doing [some refactoring ](https://github.com/esp-rs/embedded-svc/compare/unalloc) on the traits here so that all of those + the majority...

I think you have an activated esp idf environment, or at least an active python venv when trying to build the project, which is not supported (yet). Please exit all...

> I'll try esp IDF sys master tomorrow. I did have an issue with time_t not being 64bits, but adding the flag did not help, so wound up forking that...

> To use your own esp-idf repository, you should only need to set `IDF_PATH` (without sourcing `./export.sh`), and esp-idf-sys will install all the required tools in the location configured by...

> > Using an activated ESP IDF environment used to work for ESP IDF < 5. What changed in ESP IDF 5? I vaguely remember some python related issue. Can...

> but I'm not 100% sure this is necessary It is not. If the two checks (for STD and libc) don't trigger, all is OK.

Using ESP IDF 5 needs a very small upstream change to Rust STD where STD's `Cargo.toml` file is updated to use the latest version of the Rust libc crate which...

The upstream change got merged, closing.

This: https://github.com/rust-lang/rust/blob/master/library/std/Cargo.toml#L18 Basically, Rust stdlib itself had to be updated to depend on a newer version of the libc crate. Cargo is not really following the package versioning resolution across...