chore: Add CV_TRACE option to opencv recipe #27351
Open
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
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.
Summary
Changes to recipe: opencv/4.11.0
Motivation
The opencv recipe did not expose an option to toggle the CV_TRACE compile flag. This is needed to work around a known memory leak in opencv: opencv/opencv#19727
Details
Option:
cv_tracedefaulted toTrue(as this seems to be the default state from opencv CMakeLists.txt https://github.com/opencv/opencv/blob/4ad4bd5dc09b343b2be6c8137b563f143d68584d/CMakeLists.txt#L541). Will toggleCV_TRACEflag toFalseifcv_traceoption is set toFalse.