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
Copy file name to clipboardExpand all lines: docs/installation.md
+4-7
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@
4
4
5
5
- For standalone `.hs`/`.lhs` files, [ghc](https://www.haskell.org/ghc/) must be installed and on the `PATH`. The easiest way to install it is with [ghcup](https://www.haskell.org/ghcup/) or [chocolatey](https://community.chocolatey.org/packages/ghc) on Windows.
6
6
- For Cabal based projects, both ghc and [cabal-install](https://www.haskell.org/cabal/) must be installed and on the `PATH`. It can also be installed with [ghcup](https://www.haskell.org/ghcup/) or [chocolatey](https://community.chocolatey.org/packages/cabal) on Windows.
7
-
- For Stack based projects, [stack](http://haskellstack.org) must be installed and on the `PATH`.
8
7
9
8
## ghcup
10
9
@@ -26,18 +25,16 @@ More information here: <https://www.haskell.org/ghcup/guide/#hls>
26
25
27
26
## Installation from source
28
27
29
-
Direct installation from source, while possible via `cabal install exe:haskell-language-server`
30
-
and `stack install --stack-yaml stack-<GHCVER>.yaml`, is not recommended for most people.
28
+
Direct installation from source, while possible via `cabal install exe:haskell-language-server`, is not recommended for most people.
31
29
Said command builds the `haskell-language-server` binary and installs it in the default `cabal` binaries folder,
32
30
but the binary will only work with projects that use the same GHC version that built it.
33
31
34
32
### Common pre-requirements
35
33
36
-
-`stack` or `cabal` must be in your `PATH`
37
-
- You need `stack` version >= 2.1.1 or `cabal` >= 2.4.0.0
34
+
-`cabal` must be in your `PATH`
35
+
- You need `cabal` >= 2.4.0.0
38
36
-`git` must be in your `PATH`
39
-
- The directory where `stack`or `cabal` put the binaries must be in you PATH:
40
-
- For `stack` you can get it with `stack path --local-bin`
37
+
- The directory where `cabal` put the binaries must be in you PATH:
41
38
- For `cabal` it is by default `$HOME/.cabal/bin` in Linux and `%APPDATA%\cabal\bin` in windows.
42
39
43
40
Tip: you can quickly check if some command is in your path by running the command.
0 commit comments