Note that lorri looks to be a good tool for automatically doing this in the background for you, though I haven’t tested it out yet. This will need to re-build your Hoogle database, With this change, my process for adding a new dependency is: In practice, putting this all together with a few more Your project, so you’ll need to re-import your pinned nixpkgs in this shell file to get the other Note that your releaseX.nix file only exposes Install cabal this way (even if you have a globally installed cabal), so that your GHC andĬabal versions play nicely together. Whatever code block we provide when the shell is entered). (which will load programs into our nix-shell) and shellHook (which will run Notably, you’ll probably want to edit buildInputs To add more, we’ll need to “overrideĪttributes” in this env. ![]() This contained ghc/ghci, but not much else. Last time, we entered a nix shell with the env provided by our releaseX.nix by default. ![]() That works for you, great! However, I think a lot of people don’t know where to start,Īnd hopefully this will help in establishing a starting point. Be warned that the IDE section is fairly opinionated – if you have one In this post, I’ll build on that to show how you can add dependencies to yourĭev environment, then use that to bring up a no-fuss Haskell environment with a solid IDEĮxperience. I left off with a simple shell.nix file that you could use to run a local hoogle server. In the previous post from a loong time ago,
0 Comments
Leave a Reply. |