ROS launch wrapper cannot initiate the ZED SDK about zed-ros-wrapper

[prarinya-s]

I have both OpenCV2.4 and 3.0 in my machine. It seem that the ZED sdk wrapper called some of my ROS components built by OpenCV3. So I just recompile my workspace with OpenCV2.4. Problem solved.

[znculee]

I had the exactly same problem. Could you tell more detail about how to compile your workspace with OpenCV 2.4? (Not just catkin_make?) Thanks a lot!!!

[prarinya-s]

@znculee I am not sure if you have the same problem as mine. First of all, you may need to check if your opencv is built with CUDA enabled or not.

In my case, I have "cvbridge" component that particularly built for OpenCV3.0. So I just remove that component and use default cvbridge.

[znculee]

@prarinya-s I have solve it with compile wrapper package and vision_opencv package (https://github.com/ros-perception/vision_opencv) simultaneously. Thanks!

[griz1112]

ROS has its own copy of opencv. Currently with kinetic its 3.2. When you source the setup,bash script it makes sure it runs that copy of opencv. Sets it up in /tmp during runtime only. Hard to spot it since it disappears as soon as you stop the app that is using it. I have once piece of code that requires 2.4 3.1.1 and 3.2 all cuda enabled including the one that is private to ROS. In order to use cuda you have to grab the source for the ROS package and recompile it with cuda enabled. Uninstall the package from ROS install from the deb you made of opencv with cuda for ROS then reinstall ros-kinetic-desktop or whatever version you previously installed. This is the only way you can get cuda enabled opencv in ROS that will work consistently. If you try and path around it or fiddle with pkgconfig sooner or later it will bite you. ROS does this with several libraries so just because you built them with cuda enabled it doesn't mean they will be that when called by ROS. Really made a difference in the app I was building which is a monocular slam system.