Colton Idle
06/05/2021, 4:21 AMcomposables
module. Android only. This left my composables module with a build.gradle with a top level dependencies{}
block. I now converted it to multiplatform for compose desktop and so I have dependencies declared in a kotlin {}
block.
i.e.
kotlin {
android()
jvm("desktop")
sourceSets {
named("commonMain") {
dependencies {
api(compose.runtime)
api(compose.foundation)
api(compose.material)
}
}
}
}
My question (sorry for being a complete kmm noob) is that is there any reason why I would keep a top level dependencies{} block around? I still have dependencies defined there, but if I remove it then everything seems fine. When using kmm is the gist that we never use top level dependencies block?rnett
06/05/2021, 4:57 AM.kts
), there is no top level dependencies block for multiplatformColton Idle
06/05/2021, 5:06 AMrnett
06/05/2021, 5:32 AMColton Idle
06/05/2021, 2:10 PM