[Nix-dev] nix-shell for a custom haskell library
Dmitry Malikov
malikov.d.y at gmail.com
Sun May 31 12:32:34 CEST 2015
Hi Peter,
> The "env" attribute of engine-io (which is
> what nix-shell enters here) gives you an environment in which engine-io
> can be compiled.
If I remember correctly, old `haskellPackages.mkDerivation` was producing
an environment with compiled sources and installed libraries.
How to configure `shell.nix` to get `cabal configure && cabal build` done
after entering the nix-shell? What was the reason to move this step out of
nix-shell routine?
On 31 May 2015 at 12:13, Peter Simons <simons at cryp.to> wrote:
> Hi Dmitry,
>
> > After I did `nix-shell` engine-io package is not actually installed
> > inside this shell.
>
> it is not supposed to be. The "env" attribute of engine-io (which is
> what nix-shell enters here) gives you an environment in which engine-io
> can be compiled. That environment does not contain engine-io.
>
> Best regards,
> Peter
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20150531/269caf63/attachment.html
More information about the nix-dev
mailing list