-
Notifications
You must be signed in to change notification settings - Fork 196
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
YARP does not compile with OpenCV 4 #1672
Comments
It could be a good opportunity to get rid of the opencv integration inside |
They moved these classes in different headers or removed the inclusions from the "principal" headers.
compiles 👍 |
Yes, they are getting rid/transferring C code in dedicated headers. |
@Nicogene can we change the name of the issue to "YARP does not compile with OpenCV 4" so it is clear what this issue is tracking? Thanks! |
If the solution is simply add those includes if OpenCV 4 is used, probably it could make sense to add those lines to solve problems such as #1948? |
I agree to use |
Unfortunately it is not so simple, because what fixes the builds with opencv 4 breaks the builds with opencv 2, and unfortunately both in appveyor and travis(linux) there are old versions of opencv. We should use a lot of |
Wait a moment, it breaks |
If a formula is keg-only, we should just properly define the env variables so it can be found, see https://github.com/robotology/robotology-superbuild#system-dependencies-1 for Qt5 for example. |
It is keg-only because |
In theory no, in practice yes 😅 we have |
Travis now has |
I guess you meant As a side note, the link to the files in "Cellar" folder is created as For me it's building just fine now. |
There is a |
Actually I've tested. Even after uninstalling the |
Ok, thanks! Good to keep in mind! |
@nunoguedelha @claudiofantacci |
Status update: the default |
The main problem here is that debian/ubuntu don't have opencv4 yet (it is currently in debian experimental) therefore we are stuck with supporting opencv3 for a long time, but we can drop opencv2 as long as we drop support for debian stretch (oldstable) |
OpenCV 4.1.3 landed in debian testing. This means that it will also be in the next Ubuntu LTS (20.04). |
Just for the records, this means that OpenCV 3 will no longer be available on debian/ubuntu |
I started working on it some time ago, support both version 3 and 4 was a mess of #ifdef . We have to decide if we want to support only version 4 or both |
I think we can drop OpenCV 2 since we have the new icub head image with debian buster, and therefore we can drop support for debian stretch, but we will need to support both OpenCV 3 and 4 for at least 2 more years |
I disabled building YARP with OpenCV 4, since this will only cause compilation issues. |
With #2162 it compiles fine with both OpenCV 3 and 4. The question is, we want to migrate to the c++ api and leave the old OpenCV 2 api? cc @pattacini @vtikha @traversaro @drdanz @randaz81 @lornat75 @maggia80 |
I think we can merge #2162, and afterwards we can discuss if there is any advantage migrating to the new API. |
Agree with @traversaro |
Fixed by #2162 |
I pulled
opencv
andyarpdataplayer
andyarpdatadumper
doesn't compile:my
opencv_version
is4.0.0-pre
.I'm afraid that in opencv 4 they will remove
IplImage
andcvarrToMat
.We should make
yarp::sig::Image
compatible withcv::Mat
without taking account ofIplImage
.The text was updated successfully, but these errors were encountered: