Releases: antoniusnaumann/cargo-swift
v0.8.0
What's Changed
New Contributors
- @sbihel made their first contribution in #57
- @wtholliday made their first contribution in #59
Thank you for your contribution :)
Full Changelog: v0.7.1...v0.8.0
v0.7.1
What's Changed
- Use the default UniFFI Binding Generator by @neacsu in #53
- Bundle all headers and swift files for multi-crate UniFFI setups by @MarcelStruckWO in #54
- Add flags to pass through features to cargo by @MarcelStruckWO in #55
New Contributors
- @neacsu made their first contribution in #53
- @MarcelStruckWO made their first contribution in #54
Thanks for your contributions :)
Full Changelog: v0.7.0...v0.7.1
v0.7.0
- Support UniFFI 0.27
Full Changelog: v0.6.1...v0.7.0
v0.6.1
What's new
- Bugfix: Deprecation warning for dynamic libraries was shown even when building a static library. This has been fixed in this release.
Full Changelog: v0.6.0...v0.6.1
v0.6.0
What's Changed
Full Changelog: v0.5.1...v0.6.0
v0.5.1
What's Changed
- Convert dashes in lib_name to hyphens, contributed by @flisky in #41
- Introduce argument to skip toolchain check with rustup, contributed by @Eliot00 in #42
New Contributors
- @flisky made their first contribution in #41
- @Eliot00 made their first contribution in #42
Thank you for your contributions!
Full Changelog: v0.5.0...v0.5.1
v0.5.0
What's Changed
0.5.0
- Allow running
cargo swift package
in crates that only use uniffi macros - thanks to @martinmose for testing this - Add
--macro
flag tocargo swift init
to generate a project without .udl files that uses only uniffi macros - Switch to static lib by default as there is an issue with app store publishing for dynamic libs - thanks to @martinmose for pointing this out
- Silence XCode warnings in generated Swift package code - thanks to @martinmose for providing this solution
- Properly return an error exit code when an error occured
TODO: Rest of Changelog
Full Changelog: v0.4.0...v0.5.0
v0.4.0
What's Changed
0.4.0
This is a small release, mainly to update to the newest UniFFI version (and hence considered a breaking change) and fix a bug related to cargo workspaces.
- Update to UniFFI 0.24.3
- Invoking
cargo swift package
in a crate that is part of a workspace now works properly
Full Changelog: v0.3.1...v0.4.0
v0.3.1
What's Changed
0.3.1
This release brings options to choose if the library should be built as dynamic or static library and fixes a bug related to dynamic libraries. Happy building!
- Add option to specify library type to both
init
andpackage
command - Infer the library type from the crate types given in Cargo.toml if no library type was specified explicitly
- Display UniFFI error log as discussed in #21, thanks to @dylanowen for providing a suggested fix
- Fix a bug (#20) where the
@rpath
is not set correctly for dynamic libraries, thanks again to @dylanowen for pointing this out
Full Changelog: v0.3.0...v0.3.1
0.3.0
With this release, cargo swift
uses Mozilla's UniFFI for generating Swift bindings. This will allow users of cargo swift
to generate bindings to other languages supported by UniFFI from the same codebase!
- Migrate to UniFFI
- Add
--plain
flag to init command to generate a new project without example code - Show errors from failed build steps in package command
- Improve error messages
0.3.0
What's Changed
0.3.0
With this release, cargo swift
uses Mozilla's UniFFI for generating Swift bindings. This will allow users of cargo swift
to generate bindings to other languages supported by UniFFI from the same codebase!
- Migrate to UniFFI
- Add
--plain
flag to init command to generate a new project without example code - Show errors from failed build steps in package command
- Improve error messages
Full Changelog: v0.2.2...v0.3.0