-
Notifications
You must be signed in to change notification settings - Fork 117
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
protobuf version #191
Comments
Can you please give us a simple example to reproduce the issue? You can try with ros2_control_demos so simplify things |
I have solved this issue by removing protobuf I installed mannually and then reinstall probuf: |
Happy you managed to figure it out! Many thanks for submitting the solution to it, not many people do it and it's great for posterity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, in foxy version, I have tried 3.17.3 and 3.15.8 but both versions can't work and generated errors as below. I wonder I have used wrong version, what's the version suit for foxy version?
And the errors are as below:
from /home/liuchen/ROS/ros2_ws/src/gazebo_ros2_control/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp:42:
/usr/include/gazebo-11/gazebo/msgs/wrench_stamped.pb.h:203:33: error: ‘InternalMetadataWithArena’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘InternalMetadata’?
203 | ::google::protobuf::internal::InternalMetadataWithArena internal_metadata;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| InternalMetadata
/usr/include/gazebo-11/gazebo/msgs/wrench_stamped.pb.h:141:8: error: ‘bool gazebo::msgs::WrenchStamped::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream*)’ marked ‘final’, but is not virtual
141 | bool MergePartialFromCodedStream(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/gazebo-11/gazebo/msgs/wrench_stamped.pb.h:143:8: error: ‘void gazebo::msgs::WrenchStamped::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*) const’ marked ‘final’, but is not virtual
The text was updated successfully, but these errors were encountered: