The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It could be caused by python2 / python3 confusion.
Have you made sure that your PYTHONPATH env variable has no python3 directories in it?
Have you checked that Visual Studio is configured for python2; see @"ranjit kathiriya" answer to q#385096 from a few days ago.
| | 2 | No.2 Revision |
It could be caused by python2 / python3 confusion.
Have you made sure that your PYTHONPATH env variable has no python3 directories in it?
Have you checked that Visual Studio is configured for python2; see @"ranjit kathiriya" @Ranjit Kathiriya answer to q#385096 from a few days ago.
| | 3 | No.3 Revision |
It could be caused by python2 / python3 confusion.
Have you made sure that your PYTHONPATH env variable has no python3 directories in it?
Have you checked that Visual Studio is configured for python2; see @Ranjit Kathiriya answer to q#385096 #q385096 from a few days ago.
| | 4 | No.4 Revision |
It eventually becomes clear that you have compiled and installed some random version of opencv in ubuntu 18. This is a bad idea in ros. Each release of ros depends on a specific version of opencv. Installing a different version than expected will very likely cause future conflicts if you try to use any opencv-related binary packages from the ros repositories.
I have no suggestions for how you get catkin_make to see that self-compiled library.
Earlier answer:
It could be caused by python2 / python3 confusion.
Have you made sure that your PYTHONPATH env variable has no python3 directories in it?
Have you checked that Visual Studio is configured for python2; see @Ranjit Kathiriya answer to #q385096 from a few days ago.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
