RoboStack / RoboStack/ros-humble
Use rmw-zenoh-pico instead of rmw-wasm-cpp for wasm builds
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 169
- Forks
- 80
- Avg merge
- 5h 55m
- Merged PRs (30d)
- 1
Description
It would be great to remove our custom middleware now that rmw-zenoh-pico is a thing: https://github.com/esol-community/rmw_zenoh_pico
/cc @traversaro - this looks like a great use case for your recent changes to vinca in adding new recipes that are not published but have a package.xml
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
Inspect the current wasm build configuration and how vinca handles unpublished recipes with a package.xml. Compare the existing rmw-wasm-cpp setup with rmw-zenoh-pico, using the linked project as the starting point. Done means wasm builds use rmw-zenoh-pico and the custom middleware is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100