feat: add a new binding for iOS -> Swift package

[michaelx11]

Overview

The goal of this project is to ship Rust code in a format that iOS/MacOS can consume natively. This may help unblock React-Native efforts (see: issue).

Our strategy here is simple (credit to this blog post)

• Build Rust code and target iOS/MacOS resulting in libraries ".a" files
• Package those libraries into an XCFramework
• Pair this with https://github.com/xmtp/xmtp-rust-swift - a thin repo that provides a Swift package interface wrapping the XCFramework
• Consume xmtp-rust-swift via Swift Package Manager in xmtp-ios

Current Functionality

We can build xmtp-ios with xmtp-rust-swift via local XCFramework injection

Make-driven

• builds
• local XCFramework injection (or clean remote references if XCFramework bundle is hosted somewhere publicly)

Missing Functionality

Lots of room to refine the remote hosting flow. Ideally every build would put a temp object in an HTTPS accessible bucket and update the Package.swift in xmtp-rust-swift in a custom branch so devs can reference it.

[nakajima]

This is so rad. Once it lands I'll try to get it all up and running over on my end too.