Closed javoerro closed 8 months ago
Can you provide some extra details:
./idf.py build
and only fail with the vscode extension?@ivmarkov your request was added in first post, thank you!
Sorry for the late reply. I'll try to get to it in the next days.weeks. Seems to be a bug in the generated project in that the esp-idf-svc
dependency is not explicitly listed in Cargo.toml
in some cases.
In the meantime, you can add it manually.
I'm not in a rush to fix it, as anyway in the upcoming versions of esp-idf-svc
/ esp-idf-hal
/ esp-idf-sys
there is a change that would allow users to only depend on esp-idf-svc
as it will re-export the other crates.
The templates recently grew way too complex, and are now difficult to maintain - I would like to simplify the options the user can choose from. For one "all HAL", "no HAL" etc. need to go. They only serve very niche use cases, and the purpose of these templates is to bootstrap the user during her initial trials with Rust on ESP IDF. She can always adjust the Cargo.toml
manually after that.
I'm encountering the same issue on Void Linux with the latest master; the only difference is espup
version 0.7.0.
Cargo.toml
contains esp-idf-svc
as an optional dependency.
Should no longer happen with the PR which just got merged. Please reopen if you are still experiencing the issue.
Compile fails with the error: use of undeclared crate or module
esp_idf_svc
Steps to reproduce the behavior:
idf.py build
(failed in both cases)-Windows 10, vscode, espup 0.4.1 -Excerpt from the build log:
-Template parameters