Diving into Kotlin Multiplatform
summary
Kotlin 1.4 actually publishes intermediate source sets so consumers can depend on more granular APIs, and multiplatform artifacts move toward a klib-centered layout (JS and JVM have experimental klib modes). A klib is a zip with an ir folder that contains a bodies.knb file plus linkdata, resources and a manifest. Native commonization runs via a runCommonizer task that takes minutes and emits platform-specific companions; dependency inference uses a .module with variants and platform-set subset rules. Highlights: publish intermediate source sets, klib with ir and bodies.knb, runCommonizer task, Gradle module metadata variants.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:23Kotlin Publishing Model in a nutshell
- 7:18How I can play with a published library?
- 8:05Example: MPP Library in 1.3
- 34:26Do it automagically
- 35:47How can I play with the commonizer?
- 39:21What did we learn today?
related talks
01h 07mDevelop Multiplatform Projects in Kotlin
38mMultiplatfom projects with Kotlin
36mIntroducing Kotlin Multiplatform in an existing project
39mAn Overview of Multiplatform Kotlin
41mKotlin Multiplatform In Production
36mEntering the World of Other Platforms Through KMP Gate
35mIntro to Kotlin Multiplatform
30mBuilding a Multiplatform Kotlin Library