Fix OpenCV build with Visual Studio 2026#310
Merged
JanuszBedkowski merged 1 commit intoMapsHD:mainfrom Jan 16, 2026
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes a build issue when configuring the project with latest Visual Studio 2026.
When opening the CMake project in VS 2026, CMake downloads OpenCV 4.12.0, but configuration fails with:
"Found OpenCV Windows Pack but it has no binaries compatible with your configuration."
This happens because OpenCV 4.12 does not provide Windows binaries compatible with the MSVC toolset used by Visual Studio 2026. Support was added in OpenCV 4.13.
The fix updates the downloaded OpenCV version to 4.13.0 for Windows builds.
Linux builds are unchanged.
Tested with: