-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix build break with cmake 4.0 #114277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix build break with cmake 4.0 #114277
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (1)
- src/native/libs/System.Security.Cryptography.Native.Apple/CMakeLists.txt: Language not supported
cmake 4.0 no longer sets the CMAKE_OSX_SYSROOT variable for macOS targets: https://cmake.org/cmake/help/v4.0/release/4.0.html#other-changes > Builds targeting macOS no longer choose any SDK or pass an -isysroot flag to the compiler by default. Instead, compilers are expected to choose a default macOS SDK on their own. In order to use a compiler that does not do this, users must now specify -DCMAKE_OSX_SYSROOT=macosx when configuring their build. We need to stop passing the variable to swiftc in that case and rely on the default behavior.
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
/backport to release/9.0-staging |
/backport to release/8.0-staging |
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/14271928222 |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/14271930123 |
This comment was marked as outdated.
This comment was marked as outdated.
/ba-g failures are in non-osx jobs and can't be affected |
cmake 4.0 no longer sets the CMAKE_OSX_SYSROOT variable for macOS targets (this includes Mac Catalyst): https://cmake.org/cmake/help/v4.0/release/4.0.html#other-changes
We need to stop passing the variable to swiftc in that case and rely on the default behavior.
Fixes #114235
Fixes #114248