hi! Sorry if this is a Groovy question but this is...

# gradle

[Travis Reitter]

hi! Sorry if this is a Groovy question but this is blocking me from migrating to Kotlin DSL. I'm trying to figure out how to call the create() function here from a Groovy gradle file. I've tried calling this way:

cklib {
    create("sqlighter") {
        language "co.touchlab.cklib.gradle.CompileToBitcode.Language.OBJC"
    }
}

but I'm getting:

org.gradle.api.GradleScriptException: A problem occurred evaluating project ':SharedCode'.
...
Caused by: groovy.lang.MissingMethodException: No signature of method: build_89t0gtdiazmlot5b0npjl25b8.cklib() is applicable for argument types: (build_89t0gtdiazmlot5b0npjl25b8$_run_closure3) values: [build_89t0gtdiazmlot5b0npjl25b8$_run_closure3@7e7932ea]
Possible solutions: mkdir(java.lang.Object), split(groovy.lang.Closure), wait(), file(java.lang.Object), wait(long), copy(groovy.lang.Closure)

Here's a working example of it being called from Kotlin DSL.

What simple syntax error am I making? 🙂

[hfhbd]

The problem isn't create but cklib. How do you apply the plugin?

[Travis Reitter]

apply plugin: 'co.touchlab.cklib'

[hfhbd]

So not in the top plugins block? If you apply the plugin dynamically at runtime, the Kotlin compiler does not find the cklib extension at compile time.

[Travis Reitter]

thanks for reminding me. I tried changing it to this without success:

plugins {
    id 'co.touchlab.cklib'
}

[Travis Reitter]

(I didn't have a plugins block before this)

[hfhbd]

Workaround:

apply(plugin = "org.jetbrains.kotlin.jvm")

extensions.configure<org.jetbrains.kotlin.gradle.dsl.KotlinJvmProjectExtension>("kotlin") {
        explicitApi()
        sourceSets.all {
            languageSettings {
                progressiveMode = true
                optIn("kotlin.RequiresOptIn")
            }
        }
        target.compilations.all {
            kotlinOptions.allWarningsAsErrors = true
        }
    }

[Travis Reitter]

oh - I've got a kotlin block. Is it possible to work it into there or is that unrelated?

[hfhbd]

Coping the linked project should work 😄

plugins {
    kotlin("multiplatform")
    id("co.touchlab.cklib")
}

[Travis Reitter]

(this is a KMM project)

[hfhbd]

Nope, this was only a sample to call the extension block

[hfhbd]

KMM project does not matter 🙂

[Travis Reitter]

right, I didn't think so 🙂

[Travis Reitter]

I tried this:

plugins {
    kotlin("multiplatform")
    id("co.touchlab.cklib")
}

but hit

build file '.../SharedCode/build.gradle': 2: only id(String) method calls allowed in plugins {} script block

[hfhbd]

kotlin() is a Kotlin DSL only function. In Groovy, you have to use id("org.jetbrains.kotlin.jvm") I think

[Travis Reitter]

if I use that last line, I get a conflict with

apply plugin: 'org.jetbrains.kotlin.multiplatform'

because kotlin gets redefined

[Travis Reitter]

if I change the start of my file to this:

plugins {
    id("org.jetbrains.kotlin.multiplatform")
    id("co.touchlab.cklib")
}

// FIXME: cut?
//apply plugin: 'org.jetbrains.kotlin.multiplatform'
apply plugin: 'com.android.library'
apply plugin: 'com.squareup.sqldelight'
apply plugin: 'kotlinx-serialization'

I end up with the original build failure:

No signature of method: build_89t0gtdiazmlot5b0npjl25b8.cklib() is applicable for argument types [...]

[hfhbd]

Wait, I thought you want to migrate from groovy to Kotlin DSL? But I dont know, why the groovy syntax does not work, sorry

[Travis Reitter]

I do but I want to get this building and working first 🙂

[Travis Reitter]

in my migration from j2objc to KMM, I've already done a bunch of smaller migrations in the middle and it's really stretched this process out a lot more than I'd hoped. I almost always prefer to do one thing at a time to keep my sanity 🙂

[Travis Reitter]

my Gradle file isn't incredibly-complicated so maybe I'll try that migration first then try using the cklib plugin

[Vampire]

Do you have an MCVE where it fails?

[Travis Reitter]

I don't believe so but I'd have to undo some changes. I started migrating to Kotlin DSL and it hopefully shouldn't be a ton more work so I'll probably just continue on that path