Reference .kt files from a swift package manager pulled repo about xcode-kotlin

[kpgalligan]

llvm adds absolute paths to files for debugging purposes. The kotlin compiler certainly does this, and as I understand it, so does Swift. That means, if you have a binary built on your machine, you can debug it. If you get a binary from another machine (with different source paths), you can't. There are ways to fix this, which we're looking into. Packaging and distributing binaries is a big internal focus right now (both cocoapods and SPM/xcframework).

What are you using for xcframework and SPM, by the way? Curious. I've gotten xcframeworks to build locally, but haven't tried SPM integration yet.

[TrevorStoneEpic]

Oh that makes sense. Thank you for the clarification. I'll be excited to see what's coming down the line!

I currently have a pretty simple gradle task that calls out to xcodebuild and passes in the framework and dsym files to generate the xcframework and puts it in a specific frameworks folder in the github repo. I then defined a top level Package.swift file that defines a binaryTarget. Then with our standard release flow/tagging it's available for our iOS project. My biggest frustration so far is how to switch from a remote package to using a local one (don't seem to have a good alternative for something like mavenLocal), but otherwise it is an extremely easy way to have a versioned package for iOS.

The project isn't open source, but if you would like to see examples of any of those steps I would be happy to post generic versions

[kpgalligan]

Closing this. We are internally building tools for publishing and additions to the Xcode plugin to allow debugging of code built on other machines (CI, etc). This will also include SPM publishing tools.