Skip to content

Commit b6e9182

Browse files
committed
[readme] Mention swift-package-update workflow
Now that we build with HEAD, developers are more likely to need to run swift-package-udpate themselves, so mention it in the build instructions.
1 parent 49e5f39 commit b6e9182

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

README.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,14 @@ SourceKit-LSP is built using the [Swift Package Manager](https://github.com/appl
2323
For a standard debug build:
2424

2525
```sh
26+
$ swift package update
2627
$ swift build
2728
```
2829

2930
After building, the server will be located at `.build/debug/sourcekit-lsp`, or a similar path, if you passed any custom options to `swift build`. Editors will generally need to be provided with this path in order to run the newly built server - see [Editors](Editors) for more information about configuration.
3031

32+
SourceKit-LSP is designed to build against the latest SwiftPM, so if you run into any issue make sure you have the most up-to-date dependencies by running `swift package update`.
33+
3134
### Building on Linux
3235

3336
The C++ code in the index requires `libdispatch`, but unlike Swift code, it cannot find it automatically on Linux. You can work around this by adding a search path manually.

0 commit comments

Comments
 (0)