KspTaskNative is not configuration cacheable

[yigit]

KspTaskNative is not configuration cacheable due to a problem in KonanTarget. (https://youtrack.jetbrains.com/issue/KT-61657/KonanTarget-should-implement-equals-or-custom-serialization)

This especially becomes a problem due to the onlyIf check, which always fails after a KSP task is configuration cached.

I think KSP should update its onlyIf check to find the target again from HostManager using its name until the Kotlin plugin issue is fixed (to be able to keep the task cacheable).

[PaulWoitaschek]

I submitted a hotfix as it will probably take a while until this gets fixed upstream.

We have a build logic where we conditionally disable native targets based on gradle properties.

This leads to the situation that the ksp tasks are skipped even though they should not.
For more context, see:
https://kotlinlang.slack.com/archives/C013BA8EQSE/p1692613954005859

[ting-yuan]

I've merged @PaulWoitaschek's patch and it'll be available in the 1.9.10-1.0.14-SNAPSHOT tomorrow. The formal release will take a bit longer. I'm wondering if it's possible to override the Task.onlyIf check in your Gradle build scripts? E.g., Task.setOnlyIf { ... }

[yigit]

I tried that but the timing is very tricky.
When I register a configure block with task type filter, gradle calls my block before KSP 😔

[PaulWoitaschek]

You can not override it. You can only add additional statements. Gradle will then run all onlyIf blocks. It will only run the task if all evaluate to true.

Not true

    @Override
    public void setOnlyIf(final Closure onlyIfClosure) {
        taskMutator.mutate("Task.setOnlyIf(Closure)", new Runnable() {
            @Override
            public void run() {
                onlyIfSpec = createNewOnlyIfSpec().and(onlyIfClosure, "Task satisfies onlyIf closure");
            }
        });
    }

[ting-yuan]

@yigit Would wrapping that around with afterEvaluate feasible?

[ting-yuan]

I'm going to include the patch into 1.9.20-Beta-1.0.13 and later releases so that you won't need to work it around in build scripts.

[PaulWoitaschek]

Thanks! Is it safe to use the 1.9.20-Beta ksp version on 1.9.10?

It warns at configuration time:

ksp-1.9.20-Beta-1.0.13 is too new for kotlin-1.9.10. Please upgrade kotlin-gradle-plugin to 1.9.20-Beta.

[ting-yuan]

Unfortunately, no. It is built for Kotlin 1.9.20-Beta and there may be some incompatibilities to 1.9.10.

[PaulWoitaschek]

@ting-yuan
Can we get a release for 1.9.10? I'd really make use of config cache for our project.

[ting-yuan]

Do you really need Kotlin 1.9.10, or will Kotlin 1.9.20 be OK? IIUC 1.9.20 will be out very soon and KSP 1.9.20-1.0.14 will follow very closely after that.

[PaulWoitaschek]

As compose often times takes a bit longer we'd love a .10 version.