Hello folks. In the 0.7.0 kable release the depend...

# juul-libraries

[Francis Mariano]

Hello folks.
In the 0.7.0 kable release the dependency on native-mt version of Coroutines was removed. The version of Coroutines in the 0.7.0 kable is 1.5.0

The readme explains about configuration and I get a bit confusing in some points:

• Can the version of coroutine on androidMain be greater than kable coroutine version?
• Can version of coroutine (native-mt) on nativeMain be greater than kable coroutine version?
• Can the line 10 be removed?

sourceSets {
        val commonMain by getting {
            dependencies {
                implementation("com.juul.kable:core:0.7.0")  // here the version of Coroutine is 1.5.0
            }
        }

        val androidMain by getting {
            dependencies {
                implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1") // here the version of Coroutine is greater // line 10
            }
        }

        val nativeMain by creating {
            dependencies {
                implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1-native-mt") {
                    version {
                        strictly("1.5.1-native-mt")
                    }
                }
            }
        }
    }
}

[travis]

The versions of Coroutines library with and without -native-mt do not need to match. So, it is valid to use Coroutines 1.5.1 and 1.5.0 for iOS.

[travis]

Using the same version would work as well.

[travis]

The readme is also outdated, there is a PR up that updates it, and may be more understandable?

https://github.com/JuulLabs/kable/tree/twyatt/readme-gradle#multiplatform

[Francis Mariano]

I think so. Why did you remove androidMain sourceSets?

[travis]

That was a mistake. I'll fix that now. Thanks for catching it!

[travis]

Sorry, looking at it more, having Coroutines in androidMain is optional, as it is defined in commonMain.
(in the updated README in the PR linked above)

[Francis Mariano]

Ok Travis. I think that understood now. Coroutines could be optional in nativeMain too IF -native-mt is not required, right?

[travis]

Kable needs -native-mt on Native, so if you use Kable on your project on a Native target (e.g. iOS) then you'll need kotlinx-coroutines-core:$version-native-mt , but if you aren't using Kable for your Native target, then you don't need a specific version of Coroutines for that target.

[travis]

So, the whole dependency dance is because Kable needs to use the special version (-native-mt) of Coroutines, but only for Native targets.

[travis]

This will be simplified once JetBrains releases their new memory model for Native and combines the -native-mt implementation of Coroutines with the mainline Coroutines.

[Francis Mariano]

Very nice Travis. Thank you very much.

[travis]

As an example for your original question re: if the Android dependency on Coroutines (line 10) can be removed, the answer is yes, it is optional, as shown here:

https://github.com/JuulLabs/sensortag/blob/main/app/build.gradle.kts

The commonMain dependency on Coroutines provides the needed Coroutines for the Android target.

[travis]

You can optionally add a dependency in androidMain for kotlinx-coroutines-android, which adds additional Android Coroutines features.

[Francis Mariano]

Travis,

val commonMain by getting {
    dependencies {
             api("org.jetbrains.kotlinx:kotlinx-coroutines-core:${coroutinesVersion}")
             implementation("com.juul.kable:core:${kableVersion}")
         }
     }

coroutinesVersion cannot be grater than version of Coroutine in kable

[travis]

It should be fine to have a Coroutines version greater than the one used by Kable.

[travis]

For example, Kable uses Coroutines 1.5.0, but you can use 1.5.1 and it should work fine.

[travis]

As long as -native-mt is used for Native targets, the Coroutines version can be higher than Kable uses.

[Francis Mariano]

api("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1")
implementation("com.juul.kable:core:0.7.0")

That not work here. Must be another problem so. I will check here. Thank you very much again

[travis]

What is the failure you're hitting?

[Francis Mariano]

val commonMain by getting {
            dependencies {
//                api("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1")
                implementation("com.juul.kable:core:0.7.0")
            }
        }

        val iosMain by getting {
            dependencies {
                api("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1-native-mt") {
                    version {
                        strictly("1.5.1-native-mt")
                    }
                }
            }
        }

That works fine, but

val commonMain by getting {
            dependencies {
                api("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1")
                implementation("com.juul.kable:core:0.7.0")
            }
        }

        val iosMain by getting {
            dependencies {
                api("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1-native-mt") {
                    version {
                        strictly("1.5.1-native-mt")
                    }
                }
            }
        }

Fails the sync gradle

Could not resolve org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1.
Required by:
    project :shared

[Francis Mariano]

Could not resolve org.jetbrains.kotlinx:kotlinx-coroutines-core:{strictly 1.5.1-native-mt}.
Required by:
    project :shared

[Francis Mariano]

Could not resolve org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.0.
Required by:
    project :shared > com.juul.kable:core:0.7.0 > com.juul.kable:core-iosarm64:0.7.0

[travis]

Let me test this in the SensorTag sample real quick.

[travis]

Oh, your source sets that depend on iosMain needs to specify the Coroutines artifact for iOS (e.g. kotlinx-coroutines-core-iosx64).

[travis]

I assume you have other source sets that dependsOn(iosMain)?

[Francis Mariano]

No I don´t have other sources. So, I replace iosMain by iosX64Main and iosArm64Main . Works fine now.

[travis]

Perfect.

[travis]

Thanks for the feedback on the README, I've updated it to hopefully make it more clear.