Encryption part 1: Restructure SDK modules #276
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.
Currently,
:core
has build logic ensuring a copy of SQLite is bundled with all apps depending on it. That's usually what we want because the SQLite build from operating systems is either unavailable (Android) or outdated / missing extension support (Apple).However, it also means that the SQLite library can't be customized. This is an issue for users wanting to use say SQLCipher. As a first step towards that, this:
:common
(really unfortunate that:core
was taken :D) project containg virtually all sources and tests that currently live in:core
. The only difference is that this project doesn't depend onsqlite-bundled
or the:static-sqlite-driver
.:core
to mostly be an empty shell depending on:common
and the bundled SQLite dependencies.:common
to depend on:core
and bundled SQLite in its tests only.The idea is that users not wanting to depend on the regular SQLite build could customize things by depending on
:common
instead.