Always use standard MacOS package to suppress warning#56
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
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.
CMake 3.19 and above provide two Mac packages:
The 10.10 package uses OSX deployment target 10.10, while the standard
package uses 10.13. As the oldest (and now deprecated) github runner is
on 10.15 we can safely choose to use the standard package.
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
Keeping both packages available for selection causes a warning on all
MacOS builds, so we can filter out the old packages to avoid this.
#26