Add option to revert to dynamic stdlib #80
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.