RoboStack / RoboStack/robostack.github.io
Devendor cyclonedds + iceoryx
Nobody has claimed this yet.
- Dominant language
- Astro
- Stars
- 385
- Forks
- 36
- Avg merge
- 5h 37m
- Merged PRs (30d)
- 18
Description
Reminder that now cyclonedds is up to date in conda-forge cyclonedds-feedstock. The only difference is that the cyclonedds in conda-forge is not compiled against iceoryx, as it's done currently on robostack ros-rolling-cyclonedds.
In theory, I should just add iceoryx as a dep of cyclonedds and enable a compiler flag; my only question here is regarding the conda-forge philosophy. Should we build two versions of cyclonedds with and w/o the extra dep? As in knowledge_base/#multi-output-recipes, or considering it does not hurt performance, just add it as a dep?
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 by reading conda-forge's multi-output recipes guidance, then compare the cyclonedds-feedstock package with RoboStack's ros-rolling-cyclonedds build. Determine whether the iceoryx dependency and compiler flag should be shared or split into outputs; done means the packaging approach is agreed and the issue's question is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100