Closed coder0xff closed 8 months ago
If you created your project with the template and cargo-generate, than the version is determined by .cargo/config.toml inside ESP_IDF_VERSION field (e-g its determind by this env variable).
If you are using esp-idf v5 you need to pass additional compiler flags duo to the 2038 time problem that is fixed inside esp-idf 5 e.g passing "--cfg","espidf_time64",
Check the difference in the esp-template in version v4.4.6 and 5.1.2
Ok, yes. I checked that the generated project has ESP_IDF_VERSION = "v5.1.1"
and rustflags = [ "--cfg", "espidf_time64"]
so that seems correct. Do you have any advice on what I can check next?
make sure that you don't override that mention env variable manual or have others env variables set from some local / old esp-idf install you did manually.A list of all env variables that affect esp-idf-sys can be found here.
Also you can clear the .embuild dir in your project by removing it. It will download and set it up from scratch automatically.
I exited my terminal session and did a new generation. You were probably right about an environment variable being the cause. Thanks for the help @Vollbrecht
Hi. I'm running into the same problem as #238, but things were working fine yesterday and I don't know what's changed. To recap:
log.txt
238 mentions needing esp-idf 5.0 or greater installed. How do I find out what version I have installed? Or what version it's trying to use? How do I update my version?
I remembered that espup and export-esp.sh was part of figuring out the initial setup, so I was able to get this much:
Sorry if those aren't helpful. Thanks for taking a look.