tapchicoma
12/09/2018, 10:07 PMKotlinTarget
in new multiplatform plugin?
Thread in Slack Conversationh0tk3y
12/10/2018, 12:05 PMcompilations
(normally, there are main
and test
compilations) and check their kotlinSourceSets
property. Note that this will only return the source sets that are directly included into the compilations, but not those that are included due to the dependsOn
relationship. For example, a target jvm
will have its main
compilation's kotlinSourceSets
only contain jvmMain
, but not commonMain
. So you will also need to check the dependsOn
property of those source sets, recursively.tapchicoma
12/10/2018, 12:29 PMh0tk3y
12/10/2018, 6:51 PMmain
and test
which compile different source sets (production and test sources, accordingly). An Android target is even more complicated: it has a compilation per Android variant. Working with the source sets that are used in a certain compilation is much more sensible: source sets in such a group are really connected during a build and form a hierarchy of scopes.h0tk3y
12/10/2018, 6:52 PMallKotlinSourceSets
to a KotlinCompilation
may sound reasonable. I've created an issue for this: https://youtrack.jetbrains.com/issue/KT-28749tapchicoma
12/10/2018, 9:58 PM