ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

this answer help me:

Sometimes the ROS package might be looking for a particular .pc filename, like "opencv-2.3.pc", when your build of opencv 2.3 only placed a "opencv.pc" file there. Then, my solution is to create a symbolic link, in this case from "opencv.pc" to "opencv-2.3.pc" in the relevant pkgconfig path.

my actions:

sudo cp /usr/local/lib/pkgconfig/opencv.pc /usr/local/lib/pkgconfig/opencv-2.3.1.pc

edit opencv-2.3.1.pc and change 2.3.2 on 2.3.1

check:

pkg-config opencv-2.3.1 --cflags
pkg-config opencv-2.3.1 --libs

and

rosmake cv_bridge

:)

this answer help me:

Sometimes the ROS package might be looking for a particular .pc filename, like "opencv-2.3.pc", when your build of opencv 2.3 only placed a "opencv.pc" file there. Then, my solution is to create a symbolic link, in this case from "opencv.pc" to "opencv-2.3.pc" in the relevant pkgconfig path.

my actions:

sudo cp /usr/local/lib/pkgconfig/opencv.pc /usr/local/lib/pkgconfig/opencv-2.3.1.pc

edit opencv-2.3.1.pc and change 2.3.2 on 2.3.1

check:

pkg-config opencv-2.3.1 --cflags
pkg-config opencv-2.3.1 --libs

and

rosmake cv_bridge

:)it make ok, but with warning:

[ rosmake ] WARNING: Rosdep did not detect the following system dependencies as installed: opencv2.3 Consider using --rosdep-install option or rosdep install c v_bridge