on iko/ghcjs-patch-master help sign in
Note that on Cabal 3.0 you can just use "cabal build" (#744)
commit76e13925b1194ba3d66a36753a7018f7846c66f2 authorArian van Putten <arian.vanputten@gmail.com> dateFri 3 Jul 2020, 00:18 (6 years ago) parent94d758d
1 file changed+4−3
docs/tutorials/development.md+4−3
docs/tutorials/development.md+4−3
@@ -4,8 +4,8 @@ your Haskell package dependencies, but also the required system
44libraries and build tools.
55
66Inside the development shell, you can run commands such as `ghc`,
7−`ghci`, or `cabal new‑build`, and they will have all dependencies
8−available.
7+`ghci`, or `cabal new‑build` (`cabal build` on Cabal 3.0),
8+and they will have all dependencies available.
99
1010Every dependency will be cached in your Nix store. If you have set up
1111Hydra CI, then your team can share pre-built dependencies.
@@ -21,7 +21,8 @@ it exists in a file called `default.nix`.
2121 rebuild all dependencies, even though they are available in the
2222 shell. However, if you have a Stack project, you can generate the
2323 package set with Haskell.nix, then use `cabal new‑build` to work
24− on it.
24+ on it. Starting Cabal 3.0 `cabal build` will work out of the box, as
25+ new style builds are the default.
2526
2627## How to get a development shell for a package
2728