fix: silence the warnings from ExternalProject_Add #1972
Merged
Conversation
This file contains 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
CMake 3.24 introduced a change in behavior in ExternalProject_Add() regarding timestamps when extracting an archive. As updating the code would break compatibility with older CMake versions, this commit instead tells newer CMake versions to behave like older ones, using a policy setting. Note from the CMake docs: The OLD behavior of a policy is deprecated by definition and may be removed in a future version of CMake. -> so the code will have to be updated eventually, and compatibility be broken...
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.
CMake 3.24 introduced a change in behavior in ExternalProject_Add() regarding timestamps when extracting an archive.
As updating the code would break compatibility with older CMake versions, this commit instead tells newer CMake versions to behave like older ones, using a policy setting.
Note from the CMake docs:
The OLD behavior of a policy is deprecated by definition and may be removed in a future version of CMake.
-> so the code will have to be updated eventually, and compatibility be broken...