Build iOS libraries as dylibs too #135
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rkistner
approved these changes
Oct 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At the moment, the only iOS build we attach to releases is the XCFramework containing all supported targets.
For our Dart SDK, we'll likely be migrating to Dart hooks once they're stable to replace the existing build system using CocoaPods or SwiftPM. Since hooks don't really support prebuilt frameworks (they prefer being given a shared object that the Dart embedder is then responsible for processing), this adds
.dylibbuilds for the core extension on iOS. This will allow a Dart hook to download only the binary that's actually used instead of the entire framework.A small breaking change is that I've renamed the binaries for macOS (they used to be attached as
.dylib, I've renamed them to.macos.dylib). This is something to keep in mind when rolling the update into the@powersync/nodepackage, AFAIK all other consumers use the framework.