Build as a static library #134
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For a native SDK, we want to be able to distribute all of PowerSync as a single static or dynamic library. For that, we should link the core extension into that SDK to avoid users having to download multiple assets.
To unblock that work, this adapts the build and release process to build the core extension as a static SQLite extension on Desktop and Android (we may also want to do that for other Apple platforms in the future, but that's not something we need for an initial version of a native SDK). The
.a(macOS, Linux) and.lib(Windows) are also be uploaded to GitHub releases, but aren't part of another distribution.