You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the install instructions for the std toolchain from here and generated a project with cargo generate esp-rs/esp-idf-template cargo.
Locally, everything builds fine and a .embuild directory is created automatically, but in this Docker Image this does not happen.
I don't know why this happens, as far as I can tell from the layers all required dependencies are installed and I also sourced $HOME/export-esp.sh before building.
Joku1806
changed the title
esp-idf-svc fails to compile in idf-rust:esp32s3_1.73.0.1 docker image
esp-idf-sys fails to compile in idf-rust:esp32s3_1.73.0.1 docker image
Nov 8, 2023
I.e. you are trying to build esp-idf-sys for your host target, which is impossible. You should build with a target like xtensa-esp32-espidf or suchlike.
These targets are usually configured in .cargo/config.toml file inside your binary crate, but I actually don't see the .cargo directory in your project layout?
Oh yeah, that seems to work.
I am very new to rust development and saw that .cargo is a dotfile and thought that everything build-related is defined in the Cargo.toml, so I immediately added it to the .gitignore without checking it first.
Hello,
I followed the install instructions for the std toolchain from here and generated a project with
cargo generate esp-rs/esp-idf-template cargo
.Locally, everything builds fine and a .embuild directory is created automatically, but in this Docker Image this does not happen.
I don't know why this happens, as far as I can tell from the layers all required dependencies are installed and I also sourced
$HOME/export-esp.sh
before building.Here are the CI logs:
Here is the relevant part with RUST_BACKTRACE=1:
After the failed compilation, there is no
.embuild
directory:I also tried to manually add embuild using cargo add, but that did not help. Other than that, I am not sure what could be the problem.
The text was updated successfully, but these errors were encountered: