Skip to content
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

[Noetic] Use opencv3 on buster #330

Merged
merged 4 commits into from
May 19, 2020
Merged

[Noetic] Use opencv3 on buster #330

merged 4 commits into from
May 19, 2020

Conversation

sloretz
Copy link
Contributor

@sloretz sloretz commented May 18, 2020

ROS Noetic uses OpenCV 4 on Focal, but OpenCV 3.2 on Buster: https://www.ros.org/reps/rep-0003.html#noetic-ninjemys-may-2020-may-2025

  • Removes debug print added in Noetic release #323
  • If OpenCV 4 isn't available, try finding 3
  • Typedef AccessFlag type added in OpenCV 4 if using 3.2
  • Use different boost python component names on Buster vs Focal

I'm opening this PR a bit early; I'm unable to successfully run tests on my system because the cvtColorForDisplay test fails; but the import is strange. I'm wondering if it will work in the PR job:

Edit Tests pass; ready for review and hopefully merge and release 🚀

@sloretz
Copy link
Contributor Author

sloretz commented May 18, 2020

As of the latest commit tests pass for be both using Buster and Focal; the cause was a different component name for finding boost::python in Buster versus Focal.

@mjcarroll mjcarroll merged commit 55bf089 into noetic May 19, 2020
@mjcarroll mjcarroll deleted the use_opencv3_on_buster branch May 19, 2020 01:58
set(_opencv_version 3)
endif()

find_package(OpenCV ${_opencv_version4} REQUIRED

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this contains a typo and should be ${_opencv_version} not '${_opencv_version4}'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely. Linking to your PR #333

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants