-
Notifications
You must be signed in to change notification settings - Fork 226
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
Module support #270
Comments
There's already some code to parse SPM's yaml build files that was added for SPM support to SourceKitten's |
If the code is already largely written then I will have a look at implementing this soon. Should be fairly straight forward I imagine. |
vdka
added a commit
to vdka/SourceKitten
that referenced
this issue
Oct 18, 2016
Adds support for reading the build commands from the `build.yaml` file closes jpsim#270
vdka
added a commit
to vdka/SourceKitten
that referenced
this issue
Oct 18, 2016
Adds support for reading the build commands from the `build.yaml` file closes jpsim#270
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am working on a tool to parse the
.yaml
file produced by SwiftPM and use that to detect the argument's I need to pass tosourcekitten
.Current call looks like this
This work's fine until there are multiple packages. Working with Server Side Swift framework's there are a huge number of source files and when including them all
sourcekitten
times out or just doesn't respond in reasonable time.I was wondering if it were possible to pass the flags to the already build
.swiftmodule
files somehow to get them to be used for completion?The text was updated successfully, but these errors were encountered: