chore: index min_mcpp → 0.0.101 (compat.opencv per-OS feature flags)#107
Merged
Conversation
…OS feature flags (mcpp#253); older mcpp silently ignores them (backend.cpp loses __OPENCV_BUILD). Now E0006 on <0.0.101.
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
1 participant
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.
compat.opencv now uses mcpp#253 per-OS
features.<name>.flags. mcpp <0.0.101 silently ignores those keys → dnn sources lose__OPENCV_BUILD→private.hpp #error. Bumping min_mcpp makes the index reject <0.0.101 with a clear E0006 instead of a silent mis-build. (CI MCPP_VERSION is already 0.0.101 since #102.)