-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error associated with graphrhc.cpp #538
Comments
Hi @dodsonmg, your analysis is entirely correct. The thing is that the Cyclone DDS RMW layer depends on some "evolving" interfaces — a nice word for "haven't had a chance to do it properly yet" — to be precise:
The branching is to prevent regressions on released, but it doesn't mean I have completely given up on the ability to build Dashing with the current version of Cyclone (that'd be stupid). What you have run into is more like the forgetting of merging a PR on the Cyclone RMW implementation (ros2/rmw_cyclonedds#169) in the flurry of activity with Foxy and Cyclone releases. As you can see from the PR, it is trivial. It simply extends the range of Cyclone versions it works with, it doesn't break anything for older versions. Please give it a try. I did try it before doing the PR, but if you could confirm it works, that'd a much nicer endorsement for merging it. |
Thanks @eboasson. I appreciate both the quick confirmation and the additional information. I can successfully build |
Thanks! |
I'm cross-compiling ROS2 dashing for FreeBSD.
When compiling
rmw_cyclonedds_cpp
, I get the following errors:I was previously building
cyclonedds
from commit 0b50928. I think commits 9aef055 and 0006e09 made some changes associated withdds_rhc
(that I don't really understand... sorry) that might be related to my problems above.Should I be able to continue building ROS2 dashing using the the
cyclonedds
master branch?It looks like the repos file for ROS2 dashing pulls all the way back from releases/0.5.x (269f18e), but I wanted to check.
Thanks!
The text was updated successfully, but these errors were encountered: