-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Use .dylib extension for macOS dynamic libraries in XCode toolchain #14369
Use .dylib extension for macOS dynamic libraries in XCode toolchain #14369
Conversation
This is a follow-up to bazelbuild#14158. Fixes bazelbuild#11082. Closes bazelbuild#14354. PiperOrigin-RevId: 413885597 (cherrypicked from 6e1b440)
@meteorcloudy Could you merge #14360 and this PR for Bazel 5? |
@oquenchil Is this change safe to get into 5.0? |
We decided not to merge this for 5.0, see #14360 (comment) |
…acOS As of bazelbuild/bazel#14369, shared libraries produced with cc_binary on macOS with the auto-configured toolchain use the correct file extension for dynamic libraries (.dylib rather than .so). This requires adapting a test.
As of bazelbuild/bazel#14369, shared libraries produced with cc_binary on macOS with the auto-configured toolchain use the correct file extension for dynamic libraries (.dylib rather than .so). This requires adapting a test.
@meteorcloudy just so you're aware on macOS python C extensions require a |
I believe even with this PR, you can still create a shared library with a explicit |
As of bazelbuild/bazel#14369, shared libraries produced with cc_binary on macOS with the auto-configured toolchain use the correct file extension for dynamic libraries (.dylib rather than .so). This requires adapting a test.
This is a follow-up to #14158.
Fixes #11082.
Closes #14354.
PiperOrigin-RevId: 413885597
(cherrypicked from 6e1b440)