Hey Alex! Sorry for getting back on this late. Finally got some time to try this out, and was unable to get it work successfully
So in my case with the regular workflow (kicking sourcekit-lsp off through the editor extension:
- SourceKit-LSP reads buildServer.json and launches a build server proxy using the argv command specified
- SourceKit-LSP sends a
build/initializerequest to the build server proxy over the Unix domain socket - The build server proxy responds with an
InitializeBuildResultthat includes the index paths in thedatafield
However, I'm not entirely sure how to ensure buildServer.json is in my workspace / gets picked up when launching sourcekit-lsp just through the cli. Going through the above process just to build out the index-db is far more complex than just shelling out a simple init request like I used to directly to the sourcekit-lsp, so I'd like to avoid that if possible. It sounds like it should be possible if it picks up the buildServer.json when I'm just running the sourcekit-lsp executable, but I've tried creating a buildServer.json in my normal workspace root, where sourcekit-lsp executable is, etc etc all to no avail. Does the json need to be piped in to sklsp somehow?