rust-embedded / rust-embedded/meta-rust-bin
Support extra non-Linux toolchain targets
Nobody has claimed this yet.
- Dominant language
- BitBake
- Stars
- 124
- Forks
- 92
- Avg merge
- 6h 54m
- Merged PRs (30d)
- 2
Description
Applies to more than thumbv6m-none-eabi but it's the one needed for a STM32 microcontroller.
From quickly looking at it the 'rust_target' function in rust_bin-common would need to be able to return 'thumbv6m-none-eabi' so the cargo build call gets the correct target. From modifying things locally it seems changing TARGET_ARCH and TARGET_OS to match causes PROVIDES issues. So it looks like more bitbake knowledge is needed to implement a fix.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in rust_bin-common with the rust_target function and trace how TARGET_ARCH, TARGET_OS, and PROVIDES affect the cargo build call. Reproduce the local thumbv6m-none-eabi change for the STM32 target, then verify that the target is selected correctly without introducing PROVIDES issues. Done means support extends beyond thumbv6m-none-eabi without breaking existing toolchain targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100