Build error on linux and macOS about sliceropencv HOT 6 CLOSED

We aim for a green Slicer dashboard when releasing Slicer5. Therefore, we'll archive SlicerOpenCV and all extensions that rely on SlicerOpenCV, which means that they will not be attempted to be built every night. If this build issue is fixed then we'll re-enable the build.

from sliceropencv.

@lassoan I've fixed the build on Windows and Linux, but have no Mac to build/test with. Could you enable the build for a night so I can see if it passes on Mac?

from sliceropencv.

OK! What other extensions would need to be enabled (that use OpenCV and should build correctly now)?

OpenCV is a mess due to the huge amount of libraries in opencv_contrib. It would be better to avoid maintaining OpenCV builds and just use pre-built OpenCV Python wheels. Do you think this would be possible?

from sliceropencv.

Can the OpenCV from the python wheels be accessed from C++?

from sliceropencv.

The wheels only provide Python interface. But as it looks nowadays most high-level development happens in Python.

For the very rare cases when you develop low-level infrastructure in C++ then relevant parts of OpenCV can be built as a name-mangled static library using CMake superbuild.

from sliceropencv.

Ok, in this case we need to be able to access it from C++

from sliceropencv.