Zac Sweers

05/23/2023, 4:37 PM
Why were these made
in 1.9.0? Is there a different API that should be used for compiler plugins?
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:23:43: Cannot access 'NATIVE_COMPILER_PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:24:43: Cannot access 'PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:179:13: Cannot access 'PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:180:13: Cannot access 'NATIVE_COMPILER_PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'


05/23/2023, 5:24 PM
please open an issue with your use-case
It seems that these are no longer the configurations used either, as I’m seeing in our project ( that adding
add("kotlinNativeCompilerPluginClasspath", libs.androidx.compose.compiler)
to compose multiplatform projects is not resulting in the newer compose compiler actually being used. Is there a new configuration name these should be added to for
? CC @Sebastian Sellmair [JB]
> Task :backstack:compileKotlinIosSimulatorArm64 FAILED
e: This version (1.4.5) of the Compose Compiler requires Kotlin version 1.8.20 but you appear to be using Kotlin version 1.9.0-Beta which is not known to be compatible.  Please consult the Compose-Kotlin compatibility map located at <> to choose a compatible version pair (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

Sebastian Sellmair [JB]

05/30/2023, 7:13 AM
Thanks the cc! Zac, am I right, that you basically want an API where you can ‘universally’ add compiler plugin dependencies?

Zac Sweers

05/30/2023, 2:19 PM
Yep, but also curious in the meantime if the configuration used for native compilations changed in 1.9.0