Skip to content

Conversation

@charles-lunarg
Copy link
Contributor

That way it doesn't need to be updated manually in the future.

That way it doesn't need to be updated manually in the future.
@arcady-lunarg
Copy link
Contributor

Are there any compatibility issues with binaries built on latest running on older macos versions?

@charles-lunarg
Copy link
Contributor Author

Good question - I am not too sure. The macos-latest is running arm64 which may produce binaries that can't be run on x64 only macOS versions. But I cannot say what the incompatibilities between macos-13, 14, and 15 would be. @richard-lunarg may have a more concrete understanding of the situation.

@richard-lunarg
Copy link

The environment variable MACOSX_DEPLOYMENT_TARGET will affect which features of the shared runtime can be used. We've been setting this to 11.0 and the resulting binaries run all the way back to macOS 11. There's some environment variables Xcode will honor. This for example will build multi-arch binaries:
ARCHS="x86_64 arm64"
ONLY_ACTIVE_ARCH=NO

cmake will likewise honor:
CMAKE_OSX_ARCHITECTURES="x86_64;arm64"

@arcady-lunarg
Copy link
Contributor

In that case, I think we need to a) switch this to macos-latest as proposed here and b) set the deployment target, and c) enable the multiarch options as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants