chore(ui): reenable jvm

Makes the build less confusing; android builds will still succeed, but
jvm ones will fail (for now)
This commit is contained in:
Cilly Leang 2026-01-29 00:57:58 +11:00
parent 33ed389f0f
commit 30c1ba5780
Signed by: cilly
GPG key ID: 6500251E087653C9

View file

@ -18,7 +18,7 @@ kotlin {
} }
} }
// jvm() jvm()
sourceSets { sourceSets {
androidMain.dependencies { androidMain.dependencies {
@ -32,7 +32,13 @@ kotlin {
implementation(project(":core")) implementation(project(":core"))
implementation(libs.compose.runtime) implementation(libs.compose.runtime)
implementation(libs.compose.foundation) implementation(libs.compose.foundation)
// TODO: Desktop will not build
// Using upstream jetpack material3 for expressive list items in 1.5.0-alpha11
// At time of writing, cmp material3 is still on 1.5.0-alpha10
implementation(libs.compose.material3.google) implementation(libs.compose.material3.google)
// implementation(libs.compose.material3)
implementation(libs.compose.ui) implementation(libs.compose.ui)
implementation(libs.compose.components.resources) implementation(libs.compose.components.resources)
implementation(libs.compose.uiToolingPreview) implementation(libs.compose.uiToolingPreview)
@ -51,10 +57,10 @@ kotlin {
commonTest.dependencies { commonTest.dependencies {
implementation(libs.kotlin.test) implementation(libs.kotlin.test)
} }
// jvmMain.dependencies { jvmMain.dependencies {
// implementation(compose.desktop.currentOs) implementation(compose.desktop.currentOs)
// implementation(libs.kotlinx.coroutinesSwing) implementation(libs.kotlinx.coroutinesSwing)
// } }
} }
} }