Skip to content

A cargo plugin to easily build Swift packages from Rust code

License

Apache-2.0, MIT licenses found

Licenses found

Apache-2.0
LICENSE-APACHE
MIT
LICENSE-MIT
Notifications You must be signed in to change notification settings

antoniusnaumann/cargo-swift

Repository files navigation

cargo-swift

Language: Rust Crates.io Version Dependency Status

Build Publish Examples E2E Tests Clippy Dependencies

A cargo plugin to easily build Swift packages from Rust code

cargo swift provides interactive commands for initializing and packaging a Rust library as Swift Package for usage in iOS and macOS apps. This plugin uses Mozilla's UniFFI for bridging between Swift and Rust. To learn more about using UniFFI, read its User Guide, but note that you can skip the parts about generating bindings (section 2.4) and building a swift module (sections 10. and 11.) as cargo swift already takes care of this!

Getting Started

Note This plugin can only be used on macOS, since proprietary toolchains are required for this plugin to work properly.

Prerequisites

Install this plugin, simply run

cargo install cargo-swift

Installing for a different UniFFI version

Currently, cargo swift does not detect the UniFFI version of your project automatically, so for now, you have to install a matching version of cargo swift:

UniFFI cargo swift
0.25 0.5
0.26 0.6
0.27 0.7
0.28 0.8

To do so, run

cargo install [email protected] -f  

and replace 0.X with the cargo swift version you want to install.

Using cargo-swift

You can create a new library crate by running

cargo swift init

This creates a new Rust library crate with some boilerplate code and some examples to quickly get started with UniFFI. For full reference, check out this chapter of the UniFFI User Guide

To bundle the previously created Rust library as Swift Package, run:

cargo swift package

This command interactively prompts you for swift package name and target platforms. If some required toolchains for the selected target platforms are missing, cargo swift will ask you if it should install them automatically.

That's it! You can now include the created package in an iOS or macOS app via Swift Package Manager.

Configuration

As of now, configuration can only be supplied via command line arguments. Most of the time, the default should be fine - however, sometimes it might be useful to store configuration persistently. You can find a draft of how this might look in CONFIG-DRAFT.md.

License

Apache-2.0

 Copyright 2023 Antonius Naumann

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

MIT

MIT License

Copyright (c) 2023 Antonius Naumann

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.