Version 1.4.2 with improvements to xcode-build-server integration

[jansorg]

New version 1.4.2 contains improvements to integrate with xcode-build-server and BSP servers paired with sourcekit-lsp, in general.

1.4.2 is already available on the EAP channel: https://plugins.jetbrains.com/plugin/22150-swift-support/versions/eap
On the stable channel, it will become available early next week.

Earlier versions incorrectly set the working directory of the sourcekit-lsp process. It's used by sourcekit-lsp to locate the buildServer.json file in a project's base directory.
xcode-build-server is not yet bundled with the plugin and everything related to XCode is still in an early state.
I've tested this successfully with some open-source XCode projects on macOS 25 with XCode 16 and Swift 6.2.

This is an early state and later versions will hopefully provide a polished, integrated setup and experience.
I'd appreciate your feedback.

xcode-build-server setup for the plugin

• Install https://github.com/SolaWing/xcode-build-server, if you haven't already
• Build your project in XCode or run xcodebuild as explained at in this section
• Bind to XCode by creating a buildServer.json file: https://github.com/SolaWing/xcode-build-server?tab=readme-ov-file#bind-to-xcode
• Open the project's root directory in a JetBrains IDE with 1.4.2 or later of the plugin installed
• After opening a Swift file, you should have working references, code completion, etc. as usual

Other changes:

• At Preferences > Build, Execution, Deployment > Swift, there are now a few more settings to configure sourcekit-lsp launched by the plugin. The workspace type setting may help to get a XCode integration or SwiftPM setup working. But in my experience sourcekit-lsp will always use a BSP build server if there's a 'buildServer.json` file at the project root. SwiftPM etc. is detected only if that file is not present.
• More settings to better control a SwiftPM setup will follow. For example, it's sometimes necessary to set an SDK for cross-compilation or cross-platform development (e.g. iOS on macOS)
• Some more helpful actions at Tools > Swift Support for debugging and a quick restart
• Lots of parsing fixes and improvements to match Swift 6.2

Troubleshooting

I had problems to get a project with a dual SwiftPM and XCode setup working. I had to select the project.xcodeproj folder in XCode to open it. Opening the folder apparently used the SwiftPM setup and the compilation results ended up in a different place.

Make sure to use the same project.xcodeproj or project.xcworkspace files in both XCode and for the xcode-build-server setup.

Screenshots

Settings:

More actions: