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

Add option to revert to dynamic stdlib #80

Merged
merged 1 commit into from
Sep 30, 2024
Merged

Add option to revert to dynamic stdlib #80

merged 1 commit into from
Sep 30, 2024

Conversation

vzsg
Copy link
Member

@vzsg vzsg commented Sep 30, 2024

The statically linked Swift stdlib is cool, allowing for smaller images and better startup times, but not all projects are equal. Some might not run due to missing symbol errors, others might fail to build due to the increased memory pressure during build.

To alleviate this, the previous behavior is now available via a configuration variable. If SWIFT_DYNAMIC_STDLIB is defined with a non-empty value, the stdlib and Foundation remain dynamically linked, and copied into the final image, just like in the good old days.

But this time, with backtrace support.

@vzsg vzsg merged commit d73a906 into master Sep 30, 2024
@vzsg vzsg deleted the dynamic-link-option branch September 30, 2024 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant