Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Is this with cv_bridge installed from ros-jade-cv-bridge and your from-source OpenCV? If so, that is most likely the issue: binary compatibility is only guaranteed when all packages that depend on OpenCV depend on the exact same version.

Is this with cv_bridge installed from ros-jade-cv-bridge and your from-source OpenCV? If so, that is most likely the issue: binary compatibility is only guaranteed when all packages that depend on OpenCV depend on the exact same version.


Edit:

Yes, this is the case. Is there any way I can edit my CMakeList.txt to force link with another OpenCV version?

There is (something like find_package(OpenCV 3.0 REQUIRED)), but I'm not sure that is what you want.

I can install the 2.x one along with the 3.0 Do you believe is a good idea?

If you installed any ROS Jade packages that depend on cv_bridge, you should already have an OpenCV 2 version installed. The issue is that you are probably linking your executable with cv_bridge, which pulls in OpenCV 2 dependencies, but also with OpenCV 3, which won't work.

If I remember correctly, @Vincent Rabaud has been working on OpenCV 3 ROS integration. He might be able to work out the best way to do this.