I am not that familiar with iOS, can you publish in a local cocoapods like we do with mavenLocal() ?

Thanks for the update, the main functionality works as expected now! The custom preset is very handy as well. But I fail to add the following part:

binaries {
                framework {
                    baseName = "StihlConnect"
                }
            }

to the preset that I need for kotlin native to change the framework file name:

Cannot create binary debugFramework: binary with such a name already exists

any clue?

@galex you can use cocoapods to set up a local module. Using cocoapods means you dont configure the build via xcode. @Jonas Bark tracking here: https://github.com/AlecStrong/kotlin-native-cocoapods/issues/3

@alec nice!

@alec This is awesome. Thank you for this. I started working on my own fat framework task, but this does all that and more. I recall an issue previously with using more than one K/N framework in an iOS app. Is this still the case. It would be awesome to pull in Timber and other Kotlin Pods individually…

yea i havent yet tested it myself but i've also heard you cant really consume multiple K/N frameworks from an iOS app

In any case this is a great start to get Models/ViewModels ported, which is my main focus. I expect a future feature will be to push the resultant pod up to a given repo/spec repo?

interesting. You could theoretically distribute the .framework generated by K/N to a repo but i hadnt thought of that as a use case, only using it for local dev

in my mind i was thinking something like maven-publish, but cocoapods-publish or carthage-publish..

It would be awesome to be able to publish it fully like maven-publish does!