Hi, is there a difference between those options? I...

# gradle

[Tomas Kormanak]

Hi, is there a difference between those options? I see both in examples

kotlin {
    sourceSets {
        val commonMain by getting { /* ... */ }
    }
}

and

kotlin {
    sourceSets {
        commonMain { /* ... */ }
    }
}

[Javier]

you will see the difference when you need it, for example if you want to create another source set which depends on commonMain

[Tomas Kormanak]

So, I need different way to pass parameter to dependsOn() function, like this

kotlin {
    sourceSets {
        val commonMain by getting { /* ... */ }
        val jvmMain by getting { 
            dependsOn(commonMain)
        }
    }
}

and

kotlin {
    sourceSets {
        commonMain { /* ... */ }
        jvmMain { 
            dependsOn(commonMain.get())
        }
    }
}

[Tomas Kormanak]

Thanks

[Scott Kruse]

I noticed the KMP project wizard doesn't create source sets w/ dependsOn is this implicit when using multiplatform plugin?

[Scott Kruse]

e.g. expect function defined in commonMain , actual function defined in jvmMain does not require dependsOn correct?

[Javier]

you only need depends on common when you create a new source set, the default ones don't need it

[Big Chungus]

Typesafe commonMain is just a shortcut to your first example. Both are identical in terms of usage

[Javier]

they have different types

[Javier]

that is the reason you need .get()

[Big Chungus]

Then second example is safer as it's lazy

[Javier]

ah, I missunderstood you

[Big Chungus]

You can pass gradle Provider to most of the dependency APIs

[Big Chungus]

Just not together with actual types, but for that you can just invoke required dependency api twice

[Tomas Kormanak]

I am still a bit confused. e.g Why there is a commonMain and jvmMain shortcuts but not jsMain?

[Big Chungus]

Just an oversight on JB part. jvmMain is fairly new

[Big Chungus]

Also a lot more mpp projects use jvm target when compared to js