I’m struggling with linking multiple gradle module...

# kotlin-native

[Paul Woitaschek]

I’m struggling with linking multiple gradle modules together. I have 3 gradle modules that I want to merge into a single ios framework.
How would I do that?
Right now I have created an ios gradle module that just depends on the 3 modules:

kotlin {
  sourceSets {
    named("iosMain") {
      dependencies {
        api(project(":percent-distribution"))
        api(project(":podcast"))
        api(project(":units"))
      }
    }
  }
}

But that produces no frameworks

[Arkadii Ivanov]

Here is an example of exactly this use case https://github.com/arkivanov/MVIKotlin/blob/master/sample/todo-darwin-umbrella/build.gradle.kts

[Paul Woitaschek]

Thanks. I tried to adopt that but it generates nothing in the bin folder

[Arkadii Ivanov]

Did you run <target_name>MainBinaries task?

[Paul Woitaschek]

There is no Mainbinaries task

[Arkadii Ivanov]

Like iosX64MainBinaries ? It should be there, if you configured binaries correctly

[Paul Woitaschek]

Build tasks
-----------
allMetadataJar - Assembles a jar archive containing the metadata for all Kotlin source sets.
assemble - Assembles the outputs of this project.
build - Assembles and tests this project.
buildDependents - Assembles and tests this project and all projects that depend on it.
buildNeeded - Assembles and tests this project and all projects it depends on.
clean - Deletes the build directory.
compileKotlinIos - Compiles a klibrary from the 'main' compilation for target 'native'.
compileTestKotlinIos - Compiles a klibrary from the 'test' compilation for target 'native'.
iosMainKlibrary - Assembles outputs for compilation 'main' of target 'ios'
iosTestKlibrary - Assembles outputs for compilation 'test' of target 'ios'
jvmJar - Assembles an archive containing the main classes.
jvmMainClasses - Assembles outputs for compilation 'main' of target 'jvm'
jvmTestClasses - Assembles outputs for compilation 'test' of target 'jvm'
linkDebugFrameworkIos - Links a framework 'debugFramework' for a target 'ios'.
linkDebugTestIos - Links a test executable 'debugTest' for a target 'ios'.
linkReleaseFrameworkIos - Links a framework 'releaseFramework' for a target 'ios'.
metadataCommonMainClasses - Assembles outputs for compilation 'commonMain' of target 'metadata'
metadataJar - Assembles an archive containing the main classes.
metadataMainClasses - Assembles outputs for compilation 'main' of target 'metadata'

[Paul Woitaschek]

These are the tasks avilable for the ios module

[Paul Woitaschek]

I can run ./gradlew ios:iosMainBinaries but it generates nothing in the build folder

[Arkadii Ivanov]

Perhaps you should setup for each target. iosX64 and iosArm64

[Arkadii Ivanov]

There is no such a target ios

[Paul Woitaschek]

Hm thats the same. 😞

[Paul Woitaschek]

Oh wow what a crap 😄

[Paul Woitaschek]

https://github.com/arkivanov/MVIKotlin/blob/master/sample/todo-darwin-umbrella/src/commonMain/kotlin/com/arkivanov/mvikotlin/sample/todo/darwin/umbrella/Dummy.kt

[Paul Woitaschek]

This is the solution 🙈

[Arkadii Ivanov]

Ah yes! Totally forgot about this 😀

[russhwolf]

I don’t know if there’s an issue tracking that but I’m pretty sure JB is aware. The updated new project wizard adds an empty dummy source file to iOS targets in shared code when you also included an iOS application module.