public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #32653 from vaibhavsagar/patch-1

Browse Source 
Update haskell.md
This commit is contained in:
Pascal Wittmann
2017-12-14 09:08:03 +01:00
committed by GitHub
parent aacf756ed0 4bbb9fca51
commit a38ea942f5
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/languages-frameworks/haskell.md
+7 -7
View File
@@ -777,14 +777,14 @@ to find out the store path of the system's zlib library. Now, you can
stack --extra-lib-dirs=/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8/lib build stack --extra-lib-dirs=/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8/lib build
``` ```
Typically, you'll need `--extra-include-dirs` as well. It's possible Typically, you'll need `--extra-include-dirs` as well. It's possible
to add those flag to the project's `stack.yaml` or your user's to add those flag to the project's `stack.yaml` or your user's
global `~/.stack/global/stack.yaml` file so that you don't have to global `~/.stack/global/stack.yaml` file so that you don't have to
specify them manually every time. But again, you're likely better off specify them manually every time. But again, you're likely better off
using Stack's Nix support instead. using Stack's Nix support instead.
The same thing applies to `cabal configure`, of course, if you're The same thing applies to `cabal configure`, of course, if you're
building with `cabal-install` instead of Stack. building with `cabal-install` instead of Stack.
### Creating statically linked binaries ### Creating statically linked binaries