Explore >> Select a destination
|
You are here 
|
handstandsam.com | ||
| | | | |
www.marcogomiero.com
|
|
| | | | | After discovering a new interesting technology or framework, you will probably start asking yourself how to integrate it into an existing project. That's because, the possibility to start with a blank canvas is rare (not impossible, but rare). This is also the case for Kotlin Multiplatform (I'll call it KMP in the rest of the article). When starting a new blank KMP project it is easier to have a mono-repo structure like this: | |
| | | | |
johnoreilly.dev
|
|
| | | | | Amper is a new project configuration tool that JetBrains has been developing and, given some of the updates included in the recent 0.2.0 release, I thought it was time to try it out in one of the Kotlin Multiplatform samples I have (along with Fleet 1.30 which was also recently... | |
| | | | |
www.marcogomiero.com
|
|
| | | | | A few days ago, Kotlin 1.5.30 has been released. One of the features contained in the release is the official support for XCFrameworks on Kotlin Multiplatform. XCFramework is a binary that can contain multiple platform-specific variants (even for iOS and macOS at the same time). It has been introduced by Apple during the WWDC 2019 as a replacement for FatFrameworks. Before Kotlin 1.5.30, an XCFramework could be created only by running the xcrun command that will pack the frameworks for every different required platform into an XCFramework. | |
| | | | |
arturdryomov.dev
|
|
| | | Less actions via more Actions | ||
