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
Not building on esp-idf-sys master (5.1) from directory #135
Comments
Try using esp-idf-sys master (it could be related to this). Also, it seems that esp-idf-sys detected an activated esp-idf environment (i.e. after |
Well I was trying whatever I could think of to make it compile. I got it working by sourcing the export.sh and setting the IDF toolchain env to fromenv. Tbh I have no idea what needs to be set up to use a cloned version of the IDF, some more thorough documentation would be nice. |
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 too, and removing the checks.... And the code compiles and runs correctly, but seems super fishy. |
To use your own esp-idf repository, you should only need to set If you run with If there is an error installing the tools (i.e. checking the python dependencies fails), it may be worth it to remove the |
Yeah that fixed it thanks! How can I invoke tools such as otatool though? |
or idf itself? |
Do you need to use ESP IDF 5 or 5.1? See #137 |
@N3xed 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 we fix that? |
That issue where an incorrect python was used, is already fixed on master. I haven't released it yet since there could be some more changes related to esp-idf v5. It only happens when |
OK. Let's wait until #137 is fixed, we then test the |
Nuking the .embuild fixed the issue, except the TIME64 stuff. |
workaround for the time64 stuff:
I also updated my binary crate's
but I'm not 100% sure this is necessary. You will also need to add the following to
|
It is not. If the two checks (for STD and libc) don't trigger, all is OK. |
Fixed since quite some time ago. |
Hi,
Setting
in
.cargo/config.toml
, pointing to a recent clone (09f7589ef23a6b78339224efd372257a57e1be4b) of the esp-idf repository, esp-idf does not build:The text was updated successfully, but these errors were encountered: