-
Notifications
You must be signed in to change notification settings - Fork 39
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
Fails to import with swift package management in xcode #37
Comments
@sedurCode thanks for pointing out this issue! I'm not sure how we could resolve this at the moment. I use Swift on Linux and am new to XCode. I'll try to look into it and revert back. |
@sedurCode #42 might solve this issue. Can you try importing from master? |
Successfully imported from exemplary of karwa's branch. will now try from master of this branch |
Successfully imported from master of this repo. |
Although I can import and compile a program that uses example code from the README, I now get the error: |
@sedurCode do you have freetype installed on your system? If not could you try again after installing it? In case you're unable to install it using homebrew you can also install it from the source that you'll find here: https://www.freetype.org/download.html |
I only have it installed with homebrew, so I will try and alternative source |
When creating a swift application in Xcode 11 for macOS, a package.swift file is not created and linked with the project. As such I am not sure how to follow the documentation for how to include this package in my project.
As per this doc: https://developer.apple.com/documentation/xcode/adding_package_dependencies_to_your_app
It would appear apple are very keen for users to use their tool for dependency management, but as someone new to swift it obscures work-arounds.
This package repository is not accepted as a 'swift packages' dependency using the method in the article, due to the dependency on CFreeType:
Is there a way to add this package to my project given this state of affairs?
Thanks
The text was updated successfully, but these errors were encountered: