This message was deleted.

Besides that you do not "implement" something, but add a dependency to the "implementation" configuration, what you ttied works perfectly fine here:

Yeah excuse my wording, by “implementing” there I meant more like “use the

implementation

API” 😅 But yeah this does not show up for me at all, I wonder which API is it that your IDE is finding? For me none apply as seen in the attached image. Since the

fun implementation(dependencyNotation: String, configure: ExternalModuleDependency.() -> Unit): ExternalModuleDependency

one doesn’t work since libs… isn’t a string, and the

fun <T : Dependency> implementation(dependency: T, configure: T.() -> Unit): T

doesn’t work either since libs… is not a

Dependency

, but it returns a

Provider<MinimalExternalModuleDependency>

, so none of the available functions match.

D:\Dateien\.gradle\caches\7.5.1\kotlin-dsl\accessors\9825c21096ee88b996b20a7c4aa46764\sources\org\gradle\kotlin\dsl\ImplementationConfigurationAccessors.kt

Awesome thanks for sharing this! I seem to also find this in deep in my

.gradle

directory, just does not resolve for this file. Doesn’t seem to work to manually import it either hmm. Not sure if it matters that for that build.gradle.kts file I am using

kotlin("multiplatform")

instead of jvm and maybe it’s instead named something else there.

Never used KMP, so 🤷

Yeah, nevermind this, it’s not a big deal anyway. Gonna leave a normal // comment instead of now 🤷‍♂️

With KMP you use a speparate

dependencies

block that has nothing to do with the Gradle

dependencies

block. It is purley provided by the Kotlin Gradle plugin, so you need to complain to JetBrains.

Yes, I might just go ahead and do that 😅 Thanks a lot for your help!

kmp doesn’t generate accessors, it uses the interface that @Vampire has mentioned. maybe you can try

“implementation”(…) { }