Ubuntu Jammy (22) opencv4 build support. #1078
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't assume lsb_release exists.
|
Thank you very much for doing this @mikedll it should help quite a few people get started! Now merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've tested this with docker on bionic (18), focal (20), and jammy (22). By "tested", I mean I just observed that the make went down the correct path. Only jammy uses the new dependency (libdc1394-dev). I allowed the jammy build to run "make install" to completion, and the
versioncmd worked with output:I also tested this with docker on debian bullseye, and observed the older deps make path being used.