You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rebuilding the Swift package every time is not practical for use cases where custom Swift code or tests on Swift side should be added.
There are multiple solutions to this:
Keep cargo swift in control of the whole package for every build and let the user include the generated package in a separate package that handles Swift tests and code.
Use Swift Package only to generate the package. Introduce a cargo swift build command that only rebuilds the binaries and bridges.
Let the package command decide itself if a new package should be initialized or an existing one should be updated.
The text was updated successfully, but these errors were encountered:
Rebuilding the Swift package every time is not practical for use cases where custom Swift code or tests on Swift side should be added.
There are multiple solutions to this:
The text was updated successfully, but these errors were encountered: