Im trying to set some compiler args in my KMP proj...

# gradle

[Ciaran Sloan]

Im trying to set some compiler args in my KMP project, which I previously used to do via a kotlinOptions block, but since updating kotlin and AGP this seems to no longer resolve. Im reading the docs and following whats specified here, but getting the error Task with name 'compileKotlin' not found in project . I'm declaring this in the build.gradle.kts of a kmp module.

Has anyone any suggestions where I might be going wrong?

[Ciaran Sloan]

when I print the list of tasks available, I am seeing the following tasks among that list:

compileKotlinIosArm64, compileKotlinIosSimulatorArm64, compileKotlinIosX64, compileKotlinMetadata, compileLint, compileTestKotlinIosArm64, compileTestKotlinIosSimulatorArm64, compileTestKotlinIosX64

Curious as to how best to declare these compiler options without having to write this for each of these compile kotlin tasks?

[Ciaran Sloan]

some further context - I have a multi module project that has a mix of kmp and android modules. I'm using some OptIn APIs across these modules and I want to opt into these via compiler args. I'm trying to write this once in the project

[Vampire]

That example does not match the describing text, you should open a documentation bug to the Kotlin project.

The text says the example is to configure all kotlin compilation tasks, but only shows how to configure the specific compileKotlin task.

The correct example should be something like

tasks.withType<KotlinCompilationTask<*>>().configureEach {
    ...
}

[Ciaran Sloan]

ahh okay, this makes a lot of sense now! Thanks for the follow up, ill open a bug report on the docs 🙂

[mbonnin]

FWIW, you can also do that:

kotlin {
  targets.all {
    compilations.all {
      compilerOptions.configure {
      }
    }
  }
}

[Ciaran Sloan]

right, but I need context for the kotlin lambda right? So how can I do this in a multi module setup?

[mbonnin]

kotlin is the top level extension for KGP

[mbonnin]

extensions.findByName("kotlin") as KotlinMultiplatformExtension

[mbonnin]

(but usually you should just be able to write kotlin {} in a build script

[Ciaran Sloan]

I mean, yeah I'm already doing that of sorts, I have the following in a Convention plugin that im using in both android and kmp modules:

extensions.findByType<KotlinAndroidProjectExtension>()?.apply {
    jvmToolchain(17)
}
extensions.findByType<KotlinMultiplatformExtension>()?.apply {
    jvmToolchain(17)
}

[Ciaran Sloan]

but I wasnt sure how I can set compiler options in this KotlinMultiplatformExtension

[Ciaran Sloan]

but I see how your doing it above, thats helpful!

[Ciaran Sloan]

heres what I've settled with, for future if anyone happens to peek here with similar questions:

class KotlinConventionPlugin : Plugin<Project> {
    override fun apply(target: Project) {
        with(target) {
            tasks.withType<KotlinCompilationTask<*>>().configureEach {
                compilerOptions.optIn.addAll(OPT_IN_FLAGS)
            }
            extensions.findByType<KotlinAndroidProjectExtension>()?.apply {
                jvmToolchain(17)
            }
            extensions.findByType<KotlinMultiplatformExtension>()?.apply {
                jvmToolchain(17)
            }
        }
    }
}

[mbonnin]

If it's OptIn, you need, you can also do this 😅

kotlin {
  targets.all {
    sourceSets.all {
      languageSettings.optIn("org.mylibrary.OptInAnnotation")
    }
  }
}

[Ciaran Sloan]

right, but thats only specifically for KMP projects?

[mbonnin]

Yes

[Ciaran Sloan]

my use case has a mix of android and kmp projects

[mbonnin]

I'm not 100% sure why optIn would be a sourceSet vs compilation thing but I'm thinking there is a future where source sets are compiled separately

[mbonnin]

my use case has a mix of android and kmp projects

The docs has separate instructions for both, I'm not sure why TBH

[Ciaran Sloan]

yeah, I guess I could write this twice for separate android and kmp targets, but feels a bit simpler to define this once