Target management is getting a bit out of hand when adding new targets to, i.e .config/cargo.toml:
run-esp32c5 = "run --release --target riscv32imac-unknown-none-elf -p ssh-stamp-esp32 --bin ssh-stamp-esp32 --no-default-features --features board-esp32c5-devkitc"
run-esp32c61 = "run --release --target riscv32imac-unknown-none-elf -p ssh-stamp-esp32 --bin ssh-stamp-esp32 --no-default-features --features board-esp32c61-devkitc"
run-esp32c6 = "run --release --target riscv32imac-unknown-none-elf -p ssh-stamp-esp32 --bin ssh-stamp-esp32 --no-default-features --features board-esp32c6-devkitc"
(...)
This situation will progressively worsen with the combinatorial complexity of platforms * boards (see BSP support in #114).
The main motivation of doing it this way was due to keeping the build system dependencies minimal and using just plain cargo (see #40), but perhaps it's time to reconsider this strategy now that the project is growing to support more targets/architectures.
Thanks @mmalenic for the thoughts on this.
Target management is getting a bit out of hand when adding new targets to, i.e
.config/cargo.toml:This situation will progressively worsen with the combinatorial complexity of platforms * boards (see BSP support in #114).
The main motivation of doing it this way was due to keeping the build system dependencies minimal and using just plain cargo (see #40), but perhaps it's time to reconsider this strategy now that the project is growing to support more targets/architectures.
Thanks @mmalenic for the thoughts on this.