-
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
cv_bridge exposes internal GTest symbols from OpenCV and/or links incorrectly #22
Comments
can you do an ldd on your executable ? How come it is linked against OpenCV, there is no OpenCV code in there ? I replicated your code with catkin and did not get any error. |
Here is the output from
|
To be clear, I am using groovy on Ubuntu 12.04 |
wow, that is crazy. What is your gcc version ? Also, did you get the rosmake test call to work ? Or did you have to add astack.yaml or something ? |
And |
Again to clarify, it compiles the test correctly. The test itself crashes. |
The problem here is that |
Ok, was able to replicate it. |
I am not a catkin expert, but I think the real problem is in the cv_bridge CMakeLists.txt file on line 20. It adds the entire opencv library directory to the link path: I don't see the purpose of adding the entire opencv library path, when you should only include the libraries as returned by the The |
cool, that worked for me, thx. I did not think that could impact the exported tag but that makes sense. Releasing now. |
…ints_catkin_fix Fix roslib import for message module, remove roslib.load_manifest
If we create a package as follows:
and
test_opencv.cpp
containsthen we run
rosmake test
, the test compiles, but crashes on destruction.Here is the gdb output:
When I get this error, it typically is because GTest and OpenCV are fighting about symbols. In other words, OpenCV includes a version of GTest and we are linking against the wrong one.
The text was updated successfully, but these errors were encountered: