Welcome to KmpSqlencrypt Discussions! #1
skolson
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
Ask questions you’re wondering about.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we
build together 💪.
share info about coming release(s)
whatever else on-topic
Discussions about new features, new doc, new or existing issues, questions about usage are all fair game here. For example, the repo is created with one pending enhancement issue about creating a Sqldelight driver, It's preferred to only add comments directly related to the building/testing/publishing of the issue on the issue itself. Any other general discussion or questions about when to expect that issue or anything else not related to build/deploy should be in a discussion thread instead.
The library uses current Kotlin and is very close to 100% Kotlin. There is still one JNI C++ module in use for JVM deployments like Android. Everything else is Kotlin MPP or Native, with support for coroutines using the new memory management module. Discussion about any of these technologies, or the two external dependencies used by the library should happen here. It uses a custom gradle plugin for building relevant releases of SqlCipher and OpenSSL sqlcipher-openssl-build, see that repo for questions about how hese products are build from source.
The main targets for this repo are Android, JVMs, IOS, and MacOs. But it should also work on Windows with the mingwX64 builds of Sqlcipher and OpenSSL, but the build of those are currently not included . So questions/discussion of the existing or potential environments should happen here. Only a concrete enhancement request for new platform(s) like mingwX64 or vstudioX64 should be added as an enhancement issue.
The original intent of the library is to have one common interface to the Sqlite3 API, using Sqlcipher for optional database encryption, and to all have direct users (DAOs, unit tests etc) be Kotlin multiplatform, not directly from Swift or Objective-C. I have done some messing around with Swift using the framework directly, and it works, but the usage from Swift async/await logic invoking Kotlin suspend coroutines is pretty messy in my opinion. Discussions about that stuff are also welcome here.
Beta Was this translation helpful? Give feedback.
All reactions