A modern programming language that makes developers happier.

kotlinlang

Hi All,

Does anyone know if there is documentation about the wrapping of Foundation and other iOS system libraries in Kotlin?
We currently develop without code-completion, and no reference, so purely trial and error for getting the iOS part of our actual implementation.
Any documentation or github page where we can lookup stuff is appreciated.

If you’re developing on a Mac using IntelliJ and don’t have completions, there is something wrong with your setup. 

I am, and I see the same red `platform` imports as Darran Kelinske has posted last tuesday

If you use the KMM plugin in Android Studio 4.1+ and try with a new project/module created with the template, you should get autocompletion on a Mac.

Yes, we can reproduce that. I don't know what the difference is yet, we have a fairly complicated setup. I will have to dive into this sometime

I still have red imports for platform components, but it will build a framework successfully.

I have tried all of the various flags and haven't found success. Still working on it today. Will report back.

most reliable method is no HMPP, with only a single iOS target declared.

Could you please share the project at <http://kotl.in/issue|kotl.in/issue>? At least the Gradle script and environment description.

<@UJRUJP0F9> Issue has been created, with minimal project, broken and fixed: <https://youtrack.jetbrains.com/issue/KT-43192>

why did you have to do this - it seems like that should be automatic by the nature of kotlin mp
```iosMain {
    dependsOn commonMain
}```

Hello, <@UUK1B07A5>! HMPP is an abbreviation for hierarchical multiplatform programming. In fact, this is about projects structured as <https://kotlinlang.org/docs/reference/mpp-share-on-platforms.html#configure-the-hierarchical-structure-manually|here>, not a big difference from an ordinary Kotlin Multiplatform.
About explicit dependency on commonMain. As described in <https://kotlinlang.org/docs/reference/mpp-configure-compilations.html#compilation-of-the-source-set-hierarchy|the documentation>, `dependsOn` relation provide several features, and some of them might not be useful for every new source set. For example, if you want to make a project with hierarchical structure and source sets tree depth more &gt;= 4(e.g. `commonMain` -&gt; `nativeMain` for all Native targets -&gt; `appleMain` for Apple subset of Native targets -&gt; `iosX64Main`), I’m not sure making all intermediate source sets depend on the common one is a good idea.