Skip to content

Resolve conflicts and use forked SourceKit-LSP in 5.3 branch #1949

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

Merged

Conversation

MaxDesiatov
Copy link

@MaxDesiatov MaxDesiatov commented Oct 8, 2020

The fork of SourceKit-LSP allows passing the --destination option to it, which is then forwarded to SwiftPM.

The fork changes were submitted upstream in swiftlang/sourcekit-lsp#330, so most probably we won't need to use the fork in the swiftwasm branch.

Resolves #1935
Resolves #1962

@MaxDesiatov MaxDesiatov added continuous integration Improvements to continuous integration ⤵️ Upstream Tracking release Issues with the release version labels Oct 8, 2020
@MaxDesiatov MaxDesiatov marked this pull request as ready for review October 8, 2020 19:05
@MaxDesiatov MaxDesiatov force-pushed the swiftwasm-release/5.3-sourcekit-lsp branch from 8b443fd to e6e2ad3 Compare October 11, 2020 09:59
@MaxDesiatov MaxDesiatov changed the title Resolve conflicts and use forked SourceKit-LSP Resolve conflicts and use forked SourceKit-LSP in 5.3 branch Oct 11, 2020
@MaxDesiatov
Copy link
Author

@kateinoigakukun both Ubuntu 18.04 and 20.04 now fail with error: unknown type name 'uint64_t'. Do you have any suggestions?

@MaxDesiatov
Copy link
Author

I wonder if it could have anything to do with clang headers symlink that you've fixed in the swiftwasm branch? 🤔

@kateinoigakukun
Copy link
Member

kateinoigakukun commented Oct 11, 2020

I wonder if it could have anything to do with clang headers symlink that you've fixed in the swiftwasm branch? 🤔

No. That's not related. My clang headers symlink patch was required to fix issue introduced by 20995ae
However 20995ae is not included in 5.3 branch

@MaxDesiatov
Copy link
Author

It builds on Ubuntu 20.04 on Google Cloud Engine, so there's definitely something on GHA runners that breaks the build...

@kateinoigakukun
Copy link
Member

FYI: You can debug on GitHub Actions runner using https://github.com/mxschmitt/action-tmate

Looks like its headers break indexstore-db build
@MaxDesiatov
Copy link
Author

It passes! 🎉

Ready for review 🙂

@MaxDesiatov
Copy link
Author

The macOS smoke test is stuck for some reason, but that's definitely unrelated.

@MaxDesiatov MaxDesiatov merged commit 98c01ef into swiftwasm-release/5.3 Oct 13, 2020
@MaxDesiatov MaxDesiatov deleted the swiftwasm-release/5.3-sourcekit-lsp branch October 13, 2020 07:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ Upstream Tracking continuous integration Improvements to continuous integration release Issues with the release version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants