<@U2VU05RC4> the main problem of the new kotlin MP...
# multiplatform
g
@russhwolf the main problem of the new kotlin MPP is its lack of documentation. https://youtrack.jetbrains.com/issue/KT-27967
r
You're not wrong, but I've been messing with this stuff long enough that I'm used to it. There's more and more samples around that you can use as a guide but it definitely takes some understanding to get everything to fit together.
g
The problem is that for each step you have to dig: find some code somewhere, read the source, … Having an overview of the mechanisms and some simple examples (how to configurate the compiler) would help a lot.
Our project is quite big and complex (android, js, jfx) with a lot of tests,… It’s too painfull for the moment to do the migration: https://github.com/data2viz/data2viz
h
The particular point of the compiler options is somewhat covered in the Setting up Targets section (http://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#setting-up-targets). Though I agree that there's room for overall docs coverage improvements, so we'll keep improving the docs over time. Feel free to submit issues and docs pull requests for particular topics!
g
The place where the options are configured is mentioned but not the point that you need to use
compileKotlinJs
instead of the previous
compileKotlin2Js
. Some small exemples covering all the configuration possibilities would be enough for a lot of us: compiler configurations for all platforms, packaging, publishing, documentation.
n
Very much prefer the old plugin since its significantly easier to understand, more closely aligned with Gradle conventions/best practises, and it works with Gradle Kotlin DSL.