ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2017-12-06 23:15:19 -0500 | received badge | ● Famous Question (source) |
2017-07-12 08:25:51 -0500 | received badge | ● Taxonomist |
2017-06-27 03:04:22 -0500 | received badge | ● Notable Question (source) |
2017-02-08 16:08:16 -0500 | received badge | ● Popular Question (source) |
2017-01-06 02:58:09 -0500 | received badge | ● Scholar (source) |
2017-01-04 21:03:42 -0500 | received badge | ● Student (source) |
2017-01-04 15:36:13 -0500 | received badge | ● Editor (source) |
2017-01-04 15:33:09 -0500 | answered a question | cv_bridge installation error: wrong number of template arguments In the end I was able to get cv_bridge to compile by upgrading Ubilinux from Debian 7 Wheezy to 8 Jessie. It is possible that libboost1.49-dev included in Wheezy was too old for cv_bridge, and Jessie comes with libboost1.55-dev. Boost 1.53 is also the minimum version required for ROS Indigo: http://www.ros.org/reps/rep-0003.html (note that the official installation instructions for Indigo on Debian Wheezy don't mention the libboost-dev library being too old). For anyone else experiencing similar issues with ROS on Edison, there are some updated install scripts and instructions for Indigo and Kinetic available here: https://github.com/pennaerial/ros-setups |
2017-01-03 14:43:17 -0500 | asked a question | cv_bridge installation error: wrong number of template arguments I am getting an error when trying to install cv_bridge on Ubilinux (based on Debian 7 Wheezy), with ROS Indigo. The error is quoted below. I already discovered this answer: http://answers.ros.org/question/22490... However, the solution doesn't help me as it requires modifying the codebase to only work with little endian data, which I cannot guarantee. Digging through the source, it appears that cv_bridge includes the necessary boost::endian::conversion files within its source code, hence it should not require boost 1.58+ to be installed system-wide. However, compiling this included boost library creates this error. Does anyone have any ideas how to debug this error or how to fix it? Thanks in advance! (more) |
2016-06-28 20:00:42 -0500 | received badge | ● Enthusiast |
2016-06-23 08:27:00 -0500 | received badge | ● Supporter (source) |
2016-06-23 08:24:31 -0500 | commented question | Does every ROS node need to spin()? Thanks everyone! I understand it know, especially Martin's explanation that the queue is only global within the node, not across all nodes. |
2016-06-23 02:02:34 -0500 | received badge | ● Famous Question (source) |
2016-06-22 13:31:23 -0500 | received badge | ● Notable Question (source) |
2016-06-22 00:50:14 -0500 | received badge | ● Popular Question (source) |
2016-06-21 14:25:17 -0500 | asked a question | Does every ROS node need to spin()? I have been using ROS for a short time now and learned about callbacks & spinning. My question is, since be default all callbacks are added to the global callback queue, does ros::spin() in node A also process callbacks for subscribers in node B? For a specific example, in MAVROS there is a 4 thread asynchronous spinner. I built a ROS node that uses MAVROS. In my node I also use an asynchronous spinner to process callbacks; however if they both use the global callback queue then is my asynchronous spinner redundant? Thanks! |