cmake: clean cached INTERNAL variable used for 3rdparty deps#18993
Merged
opencv-pushbot merged 1 commit intoopencv:3.4from Dec 3, 2020
Merged
cmake: clean cached INTERNAL variable used for 3rdparty deps#18993opencv-pushbot merged 1 commit intoopencv:3.4from
opencv-pushbot merged 1 commit intoopencv:3.4from
Conversation
mshabunin
approved these changes
Dec 3, 2020
sl-sergei
approved these changes
Dec 3, 2020
Merged
Merged
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
4 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.
Some vars for bundled 3rdparty are set through
CACHE INTERNAL "". It is necessary to avoid conflicts with following "find_package()" calls for the same libraries (including other components, like TIFF finds ZLIB or VTK finds ZLIB, JPEG, etc).Clear such INTERNAL vars before trying "system" library.
resolves #18984
P.S. VTK doesn't really need to find JPEG (it is not used with shared libraries), but this approach is necessary to avoid breaking of our JPEG integration. See #18541