-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: No module named cv_bridge_boost on Mac OS X #17
Comments
Yes indeed. I have no experience with Mac. @wjwwood , any input on that ? Thx. It seems Python modules have to be named .so |
Sounds plausible, @venabled can you try just renaming the installed .dylib file to .so? |
Or better yet use a symbolic link? |
can you please check how other libraries do their Python compiled libraries ? e.g., is it cv2.so or dylib for OpenCV ? |
It is
|
It ends up with a SegFault if I do either symlink, or create a copy of the thing:
Here's what the directory looks like:
|
I vaguely remember it, I think that I have made a similar fix in either moveit or rqt. |
can you guys please try the fix ? (that should fix the import). There is still the segfault apparently, please provide a backtrace for that. |
I am a gdb newb, but here's my backtrace:
Was also getting a bunch of warnings from gdb in finding different object files related to boost. |
wait, so you still got the bug after my fix ? Should I reopen ? @wjwwood does that work for you ? thx |
I think this is a separate issue, I haven't reproduced it locally, but it looks like a segfault in the boost python wrapper. I would open a new issue for this (The original problem has been solved here). |
After doing the symbolic link I can do the import:
|
No sorry guys. Same segfault.
I agree with @wjwwood that it's probably something with boost::python due to the backtrace above (maybe due to the specific version of boost::python we're using in macports) I haven't put a lot of work into figuring it out and just bypassed cv_bridge for python and used PIL/numpy/opencv do do what I need to. |
I am using Homebrew, which uses boost 1.53.0 or 1.54.0 and the system provided Python, but other than that I don't know how they are different. |
make generated cmake relocatable
This seems to be related to ros-perception/image_pipeline#34
We (myself and @kyonifer) built groovy-dekstop using MacPorts on OS X 10.7.5 , and on using opencv_bridge (version 1.10.7) in python get the message:
More guessing that it has to do with something not detecting that cv_bridge_boost.dylib is created when compiling on the Mac vs cv_bridge_boost.so.
The library is compiled, and exists under $PYTHON_PATH at /opt/local/lib/python2.7/site-packages/cv_bridge/boost
Full code traceback:
The text was updated successfully, but these errors were encountered: