-
Notifications
You must be signed in to change notification settings - Fork 104
Introduce importability as a Swift package (C library). #790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #790 +/- ##
=======================================
Coverage 92.06% 92.06%
=======================================
Files 37 37
Lines 9253 9253
=======================================
Hits 8519 8519
Misses 734 734 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Thanks for the contribution! I'm not familiar with Swift. Is it possible to put everything related to Swift under the It would be good to run the tests in the CI. |
@kanru I'm afraid that the Other files are relocateable. |
I'll give it a try. |
|

This allows macOS IME developers to simply import LibChewing as a Swift Package.
The added Swift Unit Test files are only for making sure that C APIs are accessible from Swift.
On macOS, as long as libchewing is compilable using cargo, one can always run
swift teststo build and run Swift package on macOS with Xcode 26 installed (or standalone Swift 6.1+ installation). Earlier Xcode is okay as long as its shipped Swift is 6.1+.