Exclude SQLite symbols that aren't universally available #124
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
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.
This excludes
sqlite3symbols that are platform-specific or depend on optional SQLite features to ensure they're not linked by SQLiter.Because cinterop otherwise just looks at
sqlite3.hto determine symbols, it's possible that references to these symbols end up in compiled apps or frameworks when building Kotlin projects as libraries. Depending on how SQLite gets linked in the end, some of these symbols might not be available, causing linker errors.Given that these functions are not used by SQLiter, we can simply exclude them from compilation.