opencv 4.x: conan v2 support #14947
Merged
opencv 4.x: conan v2 support #14947
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
ghost
mentioned this pull request
This comment has been minimized.
This comment has been minimized.
Hooks produced the following warnings for commit 842dd91opencv/4.5.1opencv/4.5.3opencv/4.1.2opencv/4.5.5opencv/4.5.0opencv/4.5.2 |
SpaceIm
force-pushed
the
opencv-4.x-conan-v2
branch
from
842dd91 to
9350c51
Compare
Conan v1 pipelineAll green in build 2 (
Conan v2 pipeline (informative, not required for merge)Failure in build 2 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
Hooks produced the following warnings for commit 9350c51opencv/4.5.1opencv/4.5.2opencv/4.5.5opencv/4.5.0opencv/4.1.2opencv/4.5.3 |
jwillikers
approved these changes
Dec 28, 2022
1 task
prince-chrismc
approved these changes
Jan 9, 2023
AbrilRBS
pushed a commit
to AbrilRBS/conan-center-index
that referenced
this pull request
Jan 16, 2023
* bump dependencies * allow to use libjpeg implementation from mozjpeg * fix ffmpeg usage in test package * conan v2 support
|
Dear all, we face a build issue with a previously working project. Error cudafile.txt With versions:
With 4.5.5 the same error occurs.
Can you please have a look? We spent almost a day to locate this issue... It's a very bad thing that if you reference explicitly a version in conan you can still break your build because conan repository changed. |
|
Please open an issue, nobody can help with such incomplete bug report. This recipe has been migrated to conan v2 helpers and your profile may be illformed for conan v2 recipes (I don't know, just a guess). |
|
There's also a blog post :) https://blog.conan.io/2022/09/20/consuming-recipes-during-migration-conancenter.html |
|
I'm coming from the .net/java world and not really deep into the c++ stuff. However, my team has C++ projects, and some parts were written 10 years ago, pretty big projects, pure machine vision and AI-related code. For me, it would be a very basic requirement that if I reference explicitly a package in conan.txt then it builds today successfully, I can repeat this in 6, 12 months again. I shouldn't have a backup from the Conan cache and so on. Building these projects on the build server is again a misleading experience because that build is using the cache. You would assume, oh, everything is fine, it builds, tests are ok, etc. BUT, then a new developer joins the team and he needs to set up the projects from scratch... it's usually a nightmare because of issues like these. The regression testing of these changes with bigger projects is an expensive game... I don't want to blame anybody, my intention is to understand better this situation and maybe hear others how they cope with things like this. Thanks! |
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.
it's basically #13406, but only 4.x.