-
Notifications
You must be signed in to change notification settings - Fork 280
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
Update modulemap #469
Update modulemap #469
Conversation
I don't think you're supposed to include any of the |
Any idea how to silence the warnings about them? |
Looks like we should be able to exclude the headers, maybe. |
Oh! Xcode is complaining about those because they're being copied into the framework. ObjectiveGit is set up with a folder reference with all the libgit2 headers that's copied into the framework. The solution is to use a group instead of a reference so you can exclude the headers that we don't want from |
(SwiftGit2 does it this way. You should be able to use it as a reference if you need one.) |
Wouldn't this break integrations for some people that use ObjetiveGit and libgit2 directly? |
Interestingly we were already copying the headers. I'm not sure why we had the additional reference.
libgit2's headers are still exposed. This is ready for review again 🙏 |
Some of libgit2's headers are platform-dependent. We're just excluding the ones that don't apply to OS X/iOS. |
Xcode is giving me those warnings—even on |
Mostly fixes #467.
We're still getting:
But those are Windows-specific so we don't actually want them. I'm not sure how to silence the warning.