My feeling is that custom source sets don’t really create separate compilation units under MPP, they...

# multiplatform

[egorand]

My feeling is that custom source sets don’t really create separate compilation units under MPP, they just extend the default source sets but in the end get compiled into the same artifacts. Is this correct, or am I missing something?

[Dominaezzz]

Yes, this is correct.

[egorand]

Thanks! I’ll submit a feature request.

[Dominaezzz]

I just reread, unless you explicitly depend on a source set from a compilation, it doesn't get compiled.

[egorand]

In my experience, simply adding dependsOn jvmMain to a custom source set is not enough

[egorand]

The only thing that worked for me is having that source set dependsOn commonMain and then having jvmMain { dependsOn customSourceSetMain }

[egorand]

Ultimately I’m looking to something similar to this: https://docs.gradle.org/current/userguide/java_testing.html#sec:configuring_java_integration_tests

[h0tk3y]

@egorand take a look at having a custom compilation (jvm { compilations { ... } }), which actually is a separate compilation unit.

[h0tk3y]

See the end of this section: https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#configuring-compilations

[egorand]

Oh, interesting, thanks!