-
Notifications
You must be signed in to change notification settings - Fork 598
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 STILL exposes internal GTest symbols from OpenCV and/or links incorrectly #25
Comments
In the There is an explicit list of opencv libraries in the image_geometry package, but opencv_ts is missing. Hrmmm. How is that file auto-generated? |
Thx for reporting: the error was that opencv_ts is added if gtest has not been find_packaged before. Which was the case here as catkin was find_packaged AFTER OpenCV. Releasing now. |
Thanks! Do you know what the process is for moving from shadow-fixed to ros-public? It would be great if I could have this bug fix in the regular Debian package. |
Tully does that once in a while (roughly once a week) so just wait for his email on ros-users. If it's an emergency, just download the packages from here: |
make link to control messages a real link
We closed issue #22 slightly preemptively. I still have this issue with just the cv_bridge package.
If we create a package as follows:
and
test_opencv.cpp
containsthen we run
make test
, the test compiles, but crashes on destruction. This is because the library opencv_ts is linked incorrectly. I thought this was an opencv issue, but it seems like just a cv_bridge issue.If we change the package by editing the
manifest.xml
and instead depend onimage_geometry
, which still depends onopencv2
the problem is not there.Here is the comparison. With this manifest
and this command
VERBOSE=1 make tests | grep opencv_ts
. I get this line:However, with this manifest (only changing cv_bridge to image_geometry):
and this command
VERBOSE=1 make tests | grep opencv_ts
, grep fails to find opencv_ts in the link lines. But, other opencv libraries are correctly linked.So, the story here is that it must be something in the cv_bridge package that is specifically adding the opencv_ts library. I don't know why this is happening.
The text was updated successfully, but these errors were encountered: