is there a reason that the fatframework task for c...

# kotlin-native

[Josh Feinberg]

is there a reason that the fatframework task for cocoapods doesn't provide a way to generate a fat framework including x86

[Josh Feinberg]

https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/targets/native/cocoapods/KotlinCocoapodsPlugin.kt#L136

[basher]

Oh that is a bummer. The whole point of fat frameworks is that you distribute one, and then other build tooling strips out unneeded arches. This is GH issue / ticket worthy IMO

[Jonas Bark]

☝️ I agree

[svyatoslav.scherbina]

Kotlin/Native doesn’t support 32-bit iOS simulator.
What do you need this for?

[basher]

I think they meant x86_64. 32bit sim would be i386

[Josh Feinberg]

Yeah, iosX64. Realized when I went to distribute my cocoapod that you could no longer test on an emulator

[ilya.matveev]

The initial purpose of the fat framework built by the CocoaPods plugin is including this framework into a final application bundle for a device. So yes, building a framework depending on some third-party for binary distribution doesn't work out-of-the-box. But what is your specific use case? How are you trying to distribute your pod?

[Josh Feinberg]

We are trying to release a pod to our internal maven for other people to use. If they are using it in development on the simulator then they can't run it

[Josh Feinberg]

I did create the ticket - https://youtrack.jetbrains.com/issue/KT-31829 - that I see you are assigned to. happy to discuss further if you need more details

[ilya.matveev]

I see, thank you for the clarification. It looks like the most natural solution we can implement to support your use case is to avoid using a user-created Xcode project to get pods a K/N module depends on. I mean we need to download and probably build these pods under the hood of the plugin and then build K/N frameworks agains them. In this case you will be able to:
1. Build K/N module depending on pods and probably test it form command line.
2. Explicitly declare a fat framework task to build a distributable binary.

[Josh Feinberg]

Yeah, that sounds perfect