Open gentooza opened 5 months ago
Solved!
My problem was the crate elf2tab not installed.
I think setup process in Makefile should be different as it tries to execute:
setup-qemu toolchain
cargo install elf2tab
And for me qemu is not mandatory as I'm going to test this in a real device. As qemu is not installed setup process stops with an error and elf2tab was never installed.
related to issue #492
Cheers
We should do a better job of documenting which dependencies are required for writing apps (>=MSRV Rust toolchain, elf2tab... maybe that's all?) and which dependencies are needed to develop libtock-rs (specific nightly toolchain, qemu, make, probably others).
Creating automated targets to install the correct subset of our dependencies for a particular user is tricky, because different users use different dependencies. Some users deploy to boards that require tockloader and OpenOCD, others develop only in QEMU. If someone is developing an out-of-tree app, they will need elf2tab but not the libtock-rs Rust toolchains. Also, the only environment we can automatically test is the CI environment, which starts with a lot of things preinstalled (e.g. rustup) and does not have dev hardware test. So in practice, maintaining a setup
action that targets a different environment will be difficult. I think the best solution is better documentation.
Hi!
If I execute
I get:
with more debugging options using RUST_BACKTRACE=full
I'm a total newbie using rust (and pretty newbie compiling to esp32 :-D)
Cheers!