| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Summary: 269 packages finished [49min 16s] 10 packages had stderr output: cyclonedds qt_gui_cpp rmw_connext_cpp rmw_connext_shared_cpp rmw_opensplice_cpp ros1_bridge rosidl_typesupport_connext_c rosidl_typesupport_connext_cpp rosidl_typesupport_opensplice_c rosidl_typesupport_opensplice_cpp
Usually stderr are not a reason to worry. You can scroll back through the terminal to see what the errors were and decide if you care about them or not. I am assuming you are going to use the default FastRTPS DDS, meaning that the build for opensplice, cyclone and connext does not matter anyways. The ros1_bridge will also give an error if you do not have a ROS1 environment sourced (the error is probably that colcon could not find roscpp anywhere). In short these errors don't break your build and are usually insignificant.
Yeah, I'm hesitant to tell people to ignore errors. It is always good to check what the stderr is, they do point out significant flaws from time to time. In the context of building ROS2 from source though, most of the time there are some minor stderr that you don't need to pay attention to. After a while you start recognizing them and they become background noise :p. Maybe I should have chosen my words more carefully.
Asked: 2019-11-13 23:18:26 -0500
Seen: 812 times
Last updated: Nov 13 '19
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Did your build actually get aborted or did you only get stderr?
Build is not getting aborted.. Thanks for your Response..