All legacy issues aside, is there any reason to ha...
# multiplatformm
MarkRS
11/22/2021, 9:33 AMAll legacy issues aside, is there any reason to have an Android module as opposed to putting all Android code into AndroidMain in the shared module?
MarkRS
11/22/2021, 5:35 PMIs this a really hard question, or just a foolish one? No answers?
c
CLOVIS
11/22/2021, 9:05 PMI'm not really sure myself, but I think it's something to do with how the android plugin expects a specific structure, that is not compatible with Kotlin Multiplatform
e
ephemient
11/22/2021, 11:04 PMfor now, Gradle only executes tasks in different modules in parallel, no parallelism within the same module
ephemient
11/22/2021, 11:05 PMso for build performance AndroidMain sounds worse
m
MarkRS
11/23/2021, 2:05 PM@CLOVIS, that sounds interesting, can you be more specific.
@ephemient, with a (my) fairly small build that doesn't seem too much of a problem, unless there's something other than speed at stake?
e
ephemient
11/23/2021, 2:33 PMwith a small build there's not much (if anything) to be gained by parallelism, and I'm not aware of anything else significant
👍 1