-
Notifications
You must be signed in to change notification settings - Fork 414
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
Podspec mode doesn't pass through swift version 4.2 properly #1015
Comments
Clearly jazzy currently does not support Swift 4.2 (as described in Then I failed again with the following output:
which I assume the Swift versions of target project and its dependencies do not match. So I guess we need to set different versions per pod basis, maybe by passing parameters through |
@tackgyu Did you find any solution for this? I have the same problem |
@bartekzabicki Still nothing. Just have to wait for it to support Swift 4.2 |
Could this PR fix that problem: #1019 ? You can try it by installing the PR branch with https://github.com/rdp/specific_install |
@erdnussflips Thanks for the updates, but I did make it work by not passing swift version parameter at all, as: I will leave this issue open and try your suggestion if I encounter the same issue. |
Fixed in master via #1037. |
I tried generating swift docs named
TDS
using jazzy using following command:jazzy --podspec LocalPods/TDS/TDS.podspec --swift-version 4.2
and also tried with config file
.jazzy.yaml
like:using following command:
jazzy --podspec LocalPods/TDS/TDS.podspec --config LocalPods/TDS/.jazzy.yaml
but both failed with the following output:
It seems to me that the swift version I passed as paramter is somehow ignored while jazzy passing its parameters to sourcekitten, regarding the line in the output says:
RuntimeError: /Users/tackgyu/Sources/toss-ios/vendor/bundle/ruby/2.4.0/bundler/gems/jazzy-6932e5efe0eb/bin/sourcekitten ["doc", "--module-name", "TDS", "--", "-target", "TDS", "SWIFT_VERSION\\=4.0"]
.Does jazzy just not support Swift 4.2 yet, or can you at least let me know if there's a workaround for this issue if any?
The text was updated successfully, but these errors were encountered: