Skip to content
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

Allow to opt-out from library evolution #2401

Closed
wants to merge 0 commits into from

Conversation

sewerynplazuk
Copy link
Contributor

@sewerynplazuk sewerynplazuk commented Feb 16, 2024

The pull request adds support for packaging XCFrameworks that were build with library evolution disabled. Additionally it contains changes from Add the apple.no_legacy_swiftinterface feature to disable the automatic library evolution transition on framework rules PR that are essential for the packaging to work.

Copy link

google-cla bot commented Feb 16, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@brentleyjones brentleyjones changed the title Allow to opt-out form library evolution Allow to opt-out from library evolution Feb 16, 2024
@brentleyjones
Copy link
Collaborator

Additionally it contains changes from Add the apple.no_legacy_swiftinterface feature to disable the automatic library evolution transition on framework rules PR that are essential for the packaging to work

We should land cherry-picks as their own PRs. I commented in that PR as well.

@sewerynplazuk
Copy link
Contributor Author

Additionally it contains changes from Add the apple.no_legacy_swiftinterface feature to disable the automatic library evolution transition on framework rules PR that are essential for the packaging to work

We should land cherry-picks as their own PRs. I commented in that PR as well.

@brentleyjones Makes sense. Is there anything I can do to help with #2104?

@brentleyjones
Copy link
Collaborator

Is #2104 (comment) resolved?

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