Skip to content

Always set the compatibility_version of linked dylibs on Darwin. #21890

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

Merged
merged 1 commit into from
Jan 16, 2019

Conversation

DougGregor
Copy link
Member

Use 1.0.0 when there is no more-specific SWIFT_COMPILER_VERSION.

Use 1.0.0 when there is no more-specific SWIFT_COMPILER_VERSION.
@DougGregor DougGregor requested a review from gottesmm January 15, 2019 22:39
@DougGregor
Copy link
Member Author

@swift-ci please test

@jrose-apple
Copy link
Contributor

Is the default 0.0.0 not good enough?

@DougGregor
Copy link
Member Author

Is the default 0.0.0 not good enough?

With 0.0.0, I've had trouble getting the dynamic linker to accept a just-built dylib in place of one that shipped with the compiler. Having the 1.0.0 compatibility version works around that; it only affects development compilers we build ourselves.

@gottesmm
Copy link
Contributor

@DougGregor this looks ok to me. We may want to check with @Rostepher, @shahmishal, and @zisko if there are any impacts on other stuff.

@DougGregor
Copy link
Member Author

"Official" builds of Swift always have SWIFT_COMPILER_VERSION set, so it's a no-op there.

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