Hello, recently I had to use ximgproc feature, from an opencv-contrib libraries, and so I embarked on getting "full" OpenCV on my Windows 10 machine.
One setup that I managed to achieve reproducibly was via vcpkg, resulting in opencv4:x64-windows at version 4.8.0#18.
I am using a somewhat outdated rustc 1.80.0-nightly (c987ad527 2024-05-01), as this is the version before the recent breakage of -Zscript, which I am using for my OpenCV projects after switching from Python.
Attached to this is script's build log with full backtrace in system env variables and -vv flag.
92vv.log
Scripts not using features relying on non-base OpenCV package build on Windows every time, provided that opencv from vcpkg is replaced with official base installer.
As a sanity check, I have copied that script onto old Ubuntu machine with likely much older rustc, after installing libopencv-contrib-dev and pointing OPENCV_LINK_LIBS to /usr/lib/x86_64-linux-gnu, it just worked on the first attempt.
Hello, recently I had to use ximgproc feature, from an opencv-contrib libraries, and so I embarked on getting "full" OpenCV on my Windows 10 machine.
One setup that I managed to achieve reproducibly was via
vcpkg, resulting inopencv4:x64-windowsat version4.8.0#18.I am using a somewhat outdated
rustc 1.80.0-nightly (c987ad527 2024-05-01), as this is the version before the recent breakage of-Zscript, which I am using for my OpenCV projects after switching from Python.Attached to this is script's build log with full backtrace in system env variables and
-vvflag.92vv.log
Scripts not using features relying on non-base OpenCV package build on Windows every time, provided that opencv from vcpkg is replaced with official base installer.
As a sanity check, I have copied that script onto old Ubuntu machine with likely much older
rustc, after installinglibopencv-contrib-devand pointingOPENCV_LINK_LIBSto/usr/lib/x86_64-linux-gnu, it just worked on the first attempt.