Hi all, I’ve mostly got a multiplatform library working; sans a couple of issues when I attempt to a...

# multiplatform

[moltendorf]

Hi all, I’ve mostly got a multiplatform library working; sans a couple of issues when I attempt to add a few things:
• In the android `actual`s, I can’t seem to access android packages/classes (i.e. android.os.Build)
• When I add a second jvm() target (for the server), the library builds, but the android app is no longer able to resolve dependencies.

[russhwolf]

Use android() instead of jvm() for your Android target. You’ll also need to apply one of the android gradle plugins (probably com.android.library) and include an android {} block that sets minSdkVersion and compileSdkVersion.

[moltendorf]

I started doing that, but then felt at odd with the number of additional things I started adding. I guess it was right all along, so the next error about the manifest: I’ll add one and keep on in that for now?

[russhwolf]

Yeah you need a manifest too

[russhwolf]

Android plugin still needs all its usual structure

[moltendorf]

I would still use:

sourceSets["androidMain"].dependencies {
    implementation("org.jetbrains.kotlin:kotlin-stdlib")
}

?

[moltendorf]

(for initial and future dependencies) of course

[russhwolf]

yeah

[russhwolf]

though you can also add android-specific dependencies there if needed

[russhwolf]

which you can’t in a JVM target

[moltendorf]

Now I feel I should go figure out Gradle some more.

[russhwolf]

take a look through https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html

[moltendorf]

Have been. This is just my first multiplatform since I’ve been watching/learning/etc all these years.

[moltendorf]

id("com.android.*library*") yep… that fixed it I think.

[moltendorf]

Thanks for the help!

[Dariusz Rusin]

You have to keep in mind that android libs cannot be used by pure java/kotlin modules if you have some of them in project.