Dependencies and Kotlin/Native

on YouTube ↗39m

" summary

Kotlin/Native forces you to reconcile JVM artifacts and real native binaries: Gradle/Kotlin produce IR (klib) then a second compile+link step that emits architecture‑specific object code, and C interop generates headers-to-klib bindings. Using CocoaPods and Swift Package Manager or Carthage yields either vendored frameworks or source that become static or dynamic libs, which leads to the common failure mode of duplicate global symbols and App Store‑time crashes. The practical fix is static vs dynamic linking — prefer static KMP frameworks or use autolinking/linker flags to avoid duplicated symbols — and treat native warnings as urgent errors.

AI-written summary · about

" chapters (11)

1. 0:00Dependencies and Kotlin/Native
2. 2:09JVM vs native dependencies
3. 5:00Compilation and linking
4. 8:52Native symbols explained
5. 13:31Static vs dynamic libraries
6. 17:05Dynamic libraries in mobile
7. 23:16Kotlin/Native compilation
8. 28:03Static library problems
9. 34:29System libraries in Kotlin/Native
10. 35:53Warnings in native development
11. 36:59Kotlin/Native dependency best practices

" related talks

• 33mAdvanced Kotlin Native IntegrationTadeas Kriz · droidCon USA 2026
• 18mKotlin nativeMartin Bonnin · FrenchKit SE 2020
• 49mEffective Kotlin-Swift InteroperabilityJohn Rodriguez · KotlinConf 2019
• 52mBuilding apps using Kotlin NativeJeremy Rempel · droidcon NYC 2019
• 30mReusable Cross-Platform Frameworks with Kotlin/NativeSimone Civetta · Android Makers 2018
• 22mIntegrate Multiple Kotlin/Native Libraries into Your Android/iOS Apps, Vincent Nicolle Coyote SystemVincent Nicolle · Android Makers 2020
• 52mKEYNOTE: Kotlin/Native – Embracing existing ecosystemsHadi Hariri · ACCU 2018
• 43mThe Triumphs and Tribulations of Kotlin-Native in PracticeEllen Shapiro · droidcon Italy 2019