Antonius Naumann
Antonius Naumann
If there is currently nobody working on this, I would like to try to implement this (probably next week).
> All yours! > > Please don’t hesitate to ask questions here if you have any. Unfortunately I got some project deadlines the next weeks that require more work than...
Mostly convenience regarding the XCode setup and not having to maintain an additional shell script. Small difference overall, but I think that would make it less intimidating for beginners.
@chinedufn, no, it works in GUI-Apps. I embedded a Rust library using cargo xcode in a SwiftUI app that targets both macOS and iOS. What this line means: You cannot...
Alternative: Add metadata tag to workspace that specifies which libraries should be built when cargo swift is invoked in a workspace
The following behavior will be implemented: `cargo swift package` will invoke cargo metadata to detect all crates in the current workspace that have a dependency on UniFFI. The package command...
Reopening this as it introduced unwanted behavior for workspaces that contain a root package, if only the root package should be packaged.
> Can cargo-swift support `cargo swift package -p ` like `cargo build -p` does? That's the solution I currently favor, but I currently don't have time to implement this unfortunately.
Switching features dependent on target os would be a very useful feature indeed! I'll look into it, but it will take a while until I can work on this myself.
This would allow supporting new UniFFI versions without causing a breaking change.