Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix cabal install commands for local HLS build in docs #2807

Merged
merged 3 commits into from
Apr 4, 2022
Merged

Fix cabal install commands for local HLS build in docs #2807

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9cbe0fd
Fix `cabal install` commands for local HLS build
9999years Mar 29, 2022
baf6e13
Merge branch 'master' into patch-1
pepeiborra Apr 2, 2022
b754540
Merge branch 'master' into patch-1
pepeiborra Apr 4, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,13 +168,13 @@ Dynamically linked binaries (including`ghci`) use the system linker instead of t
The easiest way to obtain a dynamically linked HLS binary is to build HLS locally. With `cabal` this can be done as follows:

```bash
cabal update && cabal install pkg:haskell-language-server
cabal update && cabal install :pkg:haskell-language-server
```

If you are compiling with a ghc version with a specific `cabal-ghc${ghcVersion}.project` in the repo you will have to use it. For example for ghc-9.0.x:

```bash
cabal update && cabal install pkg:haskell-language-server --project-file=cabal-ghc90.project
cabal update && cabal install :pkg:haskell-language-server --project-file=cabal-ghc90.project
```

Or with `stack`:
Expand Down