-
Notifications
You must be signed in to change notification settings - Fork 314
Use a LocalConnection
to communicate the BSP messages between SourceKit-LSP and the build system
#1668
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
Conversation
@swift-ci Please test |
@swift-ci Please test Windows |
c0660cd
to
77102ae
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
77102ae
to
5abac15
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
5abac15
to
52a2a19
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
52a2a19
to
767eebf
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
767eebf
to
8372961
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
…nd `BuildSystem`
…`BuildSystemManager`
8372961
to
c93f193
Compare
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
@swift-ci Please test macOS |
@swift-ci Please test Linux |
This concludes the majority of the internal refactoring to BSP because the build system and SourceKit-LSP now communicate asynchronously using BSP requests. The next steps are:
FIXME
commentsBuildServerBuildSystem
and instead let theBuildSystemManager
speak directly to a build server, no longer going throughBuiltInBuildSystem
and thus opening all the new functionality for external build serversBuildSystemIntegration
module to make sure that things are named consistently, we don’t have unused methods left over.