You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This removes the requirement to suffix `*_build_test` targets at all. They are considered top-level targets now and used to collect the platform information similarly to other rules like `ios_application`
Copy file name to clipboardExpand all lines: README.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,8 @@
31
31
32
32
- Make sure your Bazel project is using compatible versions of all iOS-related Bazel rulesets (available on each release's description) and is configured to generate Swift/Obj-C indexing data and debug symbols, either by default or under a specific config.
33
33
- Detailed information around configuring Bazel flags is currently WIP, but you can currently check out the [example project](./Example) for an example.
34
-
- Make sure all libraries that you'd like to use the BSP for have accompanying `(platform)_build_test` rules that directly targets them and have a predictable suffix that includes the platform name. Example naming scheme: `(lib_name)_{ios,watchos,tvos,macos,visionos}_skbsp`
35
-
- This is because Bazel is currently missing a couple of important features we need in order to make this work in a clean way. This requirement is thus only temporary and you can expect it to be removed in the future as we evolve the tool and those missing features are introduced.
36
-
- Keep in mind that our current focus are iOS targets, so as of writing your mileage may vary when it comes to other Apple platforms.
34
+
- Make sure all libraries that you'd like to use the BSP for have accompanying top-level targets (e.g. `ios_application`, `ios_build_test`, etc.) that directly depends on them.
35
+
- Keep in mind that our current focus are iOS targets, so as of writing your mileage may vary when it comes to other Apple platforms, file an issue if you run into any problems.
37
36
- Download and install [the official Swift extension](https://marketplace.visualstudio.com/items?itemName=swiftlang.swift-vscode) for Cursor / VSCode.
38
37
- On Cursor / VSCode, open a workspace containing the repository in question.
39
38
- On the settings page for the Swift extension, enable `SourceKit-LSP: Background Indexing` at the **workspace level**. It **has** to be workspace settings; this specific setting is not supported at the folder level.
@@ -72,7 +71,7 @@ This will result in a `.bsp/skbsp.json` file being added to your workspace. User
72
71
73
72
#### After Integrating
74
73
75
-
- Reload your workspace (`Cmd+Shift+P -> Reload Window`)
74
+
- Reload your workspace (`Cmd+Shift+P -> Reload Window`) or restart the language server (`Cmd+Shift+P -> Swift: Restart LSP Server`)
76
75
77
76
After following these steps, the `SourceKit Language Server` output tab (_Cmd+Shift+U_) should show up when opening Swift or Obj-C files, and indexing-related actions will start popping up at the bottom of the IDE after a while alongside a new `SourceKit-LSP: Indexing` output tab when working with those files.
"No actions for: \(contentBeingQueried) with parent id: \(parentAction.configurationID, privacy:.public) or compile mnemonic found: \(actions.map(\.mnemonic).joined(separator:""), privacy:.public)"
0 commit comments