-
Notifications
You must be signed in to change notification settings - Fork 332
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
Can't build with Swift 5.1 with SwiftPM #151
Comments
Happy to accept a PR for this (as it relates to #150 by @aasimk2000), but personally not using SwiftPM Acceptance criteria: please no changing cmark source in any way (unless it's accepted into the upstream master repo). It needs to either work w/ build settings or SwiftPM won't be supported until that's possible |
Can you output what happens when you run |
I totally understand. I opened it in case anyone watching was interested in fixing it, but I'll definitely try to come back around when I get a chance if no one beats me to it. (And I'm also not sure how to fix this one.)
|
@iwasrobbed one potential fix I found is to move cmark_export.h and cmark_version.h to the include folder. Would this change be merged into upstream. I still have to check to see if it maintains compatibility with cocoapods and carthage. |
@aasimk2000 Personally, it feels pretty brittle to have to arbitrarily change directories (and highly doubtful that cmark would want to do that for a random / hard-to-remember-during-updates reason); there's no way to specify these explicitly in the I'd lean towards removing SwiftPM support if we can't find a way to do this cleanly |
Yup, you are right. I found another way that just require changing |
Sounds good, thanks again @aasimk2000 💯 |
Report
What did you do?
xcode-select
Xcode 11 beta 1swift build
What did you expect to happen?
It should build.
What happened instead?
This also affects building Down as a SwiftPM package using the new support in Xcode 11.
The text was updated successfully, but these errors were encountered: