You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other information that may be useful (release notes, etc...). Opencv introduced a breaking change in 4.5.1 that ended up resulting in a bug that basically stopped the entire tracking module from working (literally doesn't build) if you used the "legacy API" (which also happened to be introduced in that version, and was a breaking change on its own, though solvable from the user side). See opencv/opencv#19260. This was fixed in 4.5.2. .
Here's another project whose had to deal with similar issues: OpenShot/libopenshot#639, essentially this issue makes OpenCV 4.5.1 poison.
With out this fix I literally cannot use VCPKG with OpenCV and will have to completely remove OpenCV from all team-member VCPKG distributions.
The text was updated successfully, but these errors were encountered:
Library name: opencv4
New version number: upgrade from 4.5.1 -> 4.5.2
Other information that may be useful (release notes, etc...). Opencv introduced a breaking change in 4.5.1 that ended up resulting in a bug that basically stopped the entire tracking module from working (literally doesn't build) if you used the "legacy API" (which also happened to be introduced in that version, and was a breaking change on its own, though solvable from the user side). See opencv/opencv#19260. This was fixed in 4.5.2. .
Here's another project whose had to deal with similar issues: OpenShot/libopenshot#639, essentially this issue makes OpenCV 4.5.1 poison.
With out this fix I literally cannot use VCPKG with OpenCV and will have to completely remove OpenCV from all team-member VCPKG distributions.
The text was updated successfully, but these errors were encountered: