You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a linking error while building the gazebo_ros package on Windows. The build process fails with an unresolved external symbol related to Google's protobuf library. Below are the relevant details from the build log:
The error occurs with gazebo_ros_init (gazebo_ros) and gazebo_ros_ray_sensor (gazebo_plugins).
System Information:
OS: Windows 11 Pro
ROS 2 Distro: Humble
Compiler: MSVC (Visual Studio 2019)
Build Tool: CMake
Gazebo version: 11.14.0
vcpkg: ignition-msgs5:x64-windows (Version 5.3.0#7) and protobuf:x64-windows (4.25.1#1 )
Steps to Reproduce:
Clone the gazebo_ros_pkgs repository.
Attempt to build the package using colcon or CMake.
Observe the linker error during the build.
Additional Information:
I have installed protobuf using vcpkg and confirmed that the required libraries are available in my system. However, the linker still fails to resolve the MessageLite::ParseFromString symbol.
Any assistance or guidance to resolve this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hello ROS Developers,
I encountered a linking error while building the
gazebo_ros
package on Windows. The build process fails with an unresolved external symbol related to Google'sprotobuf
library. Below are the relevant details from the build log:The error occurs with gazebo_ros_init (gazebo_ros) and gazebo_ros_ray_sensor (gazebo_plugins).
System Information:
vcpkg: ignition-msgs5:x64-windows (Version 5.3.0#7) and protobuf:x64-windows (4.25.1#1 )
Steps to Reproduce:
gazebo_ros_pkgs
repository.colcon
orCMake
.Additional Information:
I have installed
protobuf
usingvcpkg
and confirmed that the required libraries are available in my system. However, the linker still fails to resolve theMessageLite::ParseFromString
symbol.Any assistance or guidance to resolve this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: