ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
To compile a workspace with a specific version of OpenCV ( for exemple a version with Cuda ) see : https://answers.ros.org/question/272390/compile-with-different-opencv/#272442
You can look either at the accepted answer there or at my answer.
I don't believe you have any interest in recompiling all the packages included in the kinetic distribution (like CV_bridge) using a cuda enabled version of openCV. For your own packages, you should be working inside a workspace and in that case thelink is exactly what you need
Ps : a fast thought, what happen if you erase the build and devel directory of your workspace and compile using your current cmakefile ( in which the exact OpenCV path is specified ) ?
2 | No.2 Revision |
To compile a workspace with a specific version of OpenCV ( for exemple a version with Cuda ) see : https://answers.ros.org/question/272390/compile-with-different-opencv/#272442
You can look either at the accepted answer there or at my answer.
I don't believe you have any interest in recompiling all the packages included in the kinetic distribution (like CV_bridge) using a cuda enabled version of openCV. For your own packages, you should be working inside a workspace and in that case thelink is exactly what you need
Ps : a fast thought, what happen if you erase the build and devel directory of your workspace and compile using your current cmakefile ( in which the exact OpenCV path is specified ) ?
For the set(catkin_LIBRAIRIES first_lib_you_want; second_lib_you_want; ...), what you want to do is run your cmakelist one time printing the catkin_LIBRAIRIES and then you want to keep everything that's not an OpenCV lib and those are the libs you want to keep in your set.
3 | No.3 Revision |
To compile a workspace with a specific version of OpenCV ( for exemple a version with Cuda ) see : https://answers.ros.org/question/272390/compile-with-different-opencv/#272442
You can look either at the accepted answer there or at my answer.
I don't believe you have any interest in recompiling all the packages included in the kinetic distribution (like CV_bridge) using a cuda enabled version of openCV. For your own packages, you should be working inside a workspace and in that case thelink is exactly what you need
Ps : a fast thought, what happen if you erase the build and devel directory of your workspace and compile using your current cmakefile ( in which the exact OpenCV path is specified ) ?
Edit: For the set(catkin_LIBRAIRIES first_lib_you_want; second_lib_you_want; ...), what you want to do is run your cmakelist one time printing the catkin_LIBRAIRIES and then you want to keep everything that's not an OpenCV lib and those are the libs you want to keep in your set.