You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should investigate what we need to do in order to support mergeable libraries.
A few points after watching the WWDC video:
Mergeable libraries are basically dylibs/frameworks that contain enough information to act as static libraries as well, which about doubles their size.
The consumer of mergeable libraries decide if they want the dynamic or the static version of it.
Only the new linker can consume the static version of mergeable libraries.
I suspect mergeable libraries will work without any changes on our side, because we'll see them and treat them as standard dynamic libraries / frameworks.
However, we won't remove the static bits from them when putting them into the app bundle, so app size will be increased unless we add support for removing static bits from mergeable libraries.
So first task would be:
Investigate how Xcode removes static bits from mergeable libraries.
Implement what Xcode does in our own code.
Then additionally:
Investigate what we need to do in order to support linking statically with mergable libraries.
Implement it, if we so desire.
The text was updated successfully, but these errors were encountered:
Ref: https://developer.apple.com/videos/play/wwdc2023/10268/
We should investigate what we need to do in order to support mergeable libraries.
A few points after watching the WWDC video:
I suspect mergeable libraries will work without any changes on our side, because we'll see them and treat them as standard dynamic libraries / frameworks.
However, we won't remove the static bits from them when putting them into the app bundle, so app size will be increased unless we add support for removing static bits from mergeable libraries.
So first task would be:
Then additionally:
The text was updated successfully, but these errors were encountered: