jvm sqlite driver support splits native binary

[Caij]

jvm sqlite driver support splits native binary

[kevincianfarini]

What exactly is the question here? Are you trying to cut down on the binary size of the sqlite driver on JVM by restricting the amount of platforms it supports?

If so, that won't work. The JVM is meant to run on a large array of platforms. Since SQLite drivers are written in C code, to interface with that Java code has to wrap a binary built for each specific platform to interop with it.

Reducing the binary size of the driver by removing these folders is tantamount to removing JVM support for those platforms altogether. That is the opposite of the goal of the JVM.

[Caij]

What exactly is the question here? Are you trying to cut down on the binary size of the sqlite driver on JVM by restricting the amount of platforms it supports?

If so, that won't work. The JVM is meant to run on a large array of platforms. Since SQLite drivers are written in C code, to interface with that Java code has to wrap a binary built for each specific platform to interop with it.

Reducing the binary size of the driver by removing these folders is tantamount to removing JVM support for those platforms altogether. That is the opposite of the goal of the JVM.

Yes, I would like to provide dependency packages for different platforms, as developers are aware of the target system when packaging jvm app.

eg:
implementation("app.cash.sqldelight:sqlite-driver-mac")
implementation("app.cash.sqldelight:sqlite-driver-win")

[JakeWharton]

You can request that from the JDBC sqlite driver which provides these binaries. We do not package sqlite.

If they decide to package platform-specific variants, you could exclude our multiplatform dependency and include the platform-specific one in your build.

In general, though, we want to use the artifact which packages for every platform.

[Caij]

ok, thanks