-
Notifications
You must be signed in to change notification settings - Fork 134
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
Unable to build with extra component esp-camera #371
Comments
Don't mix esp-hal and esp-idf-sys. They are separate projects, e.g esp-hal is standalone baremetall, and esp-idf-sys is running on-top of FreeRTOS using the esp-idf sdk. |
ok but even removing the esp-hal dependency doesn't solve the issue |
same goes for esp-println and esp-backtrace. Also what is your reasoning for providing nostartfiles and default linker libraries as rustflags? |
Ah you did not use the esp-idf-template in the first place but the esp generate tool? Yeah please use the esp-idf-template as a base. Than just adding the esp-camera module should get you the bindings. |
Yea that was the issue, thanks for the help. just out of pure curiosity, how do i know which function is std-only in esp-idf-svc? |
It does not make any sense to use
What is NOT allowed / wrong is to mix the You have to choose ONE framework (ESP-IDF, and thus STD) OR the other (no ESP-IDF and no STD as Usually choosing one or the other is deciding on the trade-off between having more drivers or a need to interop with an existing C codebase (ESP-IDF) vs more "pure Rust" and less memory and flash size consumption ( Once you choose ESP-IDF or baremetal however, you can still use most of the generic crates from the Embassy echosystem if you want to go async. As well as (for ESP-IDF specifically) some low-footprint generic STD-only crates. Using generic no_std crates like - say - |
Bug description
I have been trying to build the template generated by esp-generate by only adding the necessary code in the toml to compile with the extra component esp-camera, however it doesn't find the xtensa toolchain
To Reproduce
cargo.toml:
.cargo/config.toml:
error log:
Environment
ESP-IDF v5.3
toolchain installed from through espup
Target device (MCU): esp32 (in the path the following commands for xtensa-esp32 are present:
xtensa-esp32-elf-addr2line xtensa-esp32-elf-gcc-14.2.0 xtensa-esp32-elf-lto-dump
xtensa-esp32-elf-ar xtensa-esp32-elf-gcc-ar xtensa-esp32-elf-nm
xtensa-esp32-elf-as xtensa-esp32-elf-gcc-nm xtensa-esp32-elf-objcopy
xtensa-esp32-elf-c++ xtensa-esp32-elf-gcc-ranlib xtensa-esp32-elf-objdump
xtensa-esp32-elf-cc xtensa-esp32-elf-gcov xtensa-esp32-elf-ranlib
xtensa-esp32-elf-c++filt xtensa-esp32-elf-gcov-dump xtensa-esp32-elf-readelf
xtensa-esp32-elf-cpp xtensa-esp32-elf-gcov-tool xtensa-esp32-elf-size
xtensa-esp32-elf-elfedit xtensa-esp32-elf-gdb xtensa-esp32-elf-strings
xtensa-esp32-elf-g++ xtensa-esp32-elf-gprof xtensa-esp32-elf-strip
xtensa-esp32-elf-gcc xtensa-esp32-elf-ld
xtensa-esp32-elf-gcc-13.2.0 xtensa-esp32-elf-ld.bfd )
OS: EndeavourOS x86_64 Linux 6.13.1-zen3-1-zen
The text was updated successfully, but these errors were encountered: