[Nix-dev] break purity
Oliver Charles
ollie at ocharles.org.uk
Fri Apr 22 18:54:29 CEST 2016
Well you don't tie the knot in the expression itself. It's more that the
pre-existing artefacts are a function input, and a function output:
{ stdenv, gcc, etc, artefacts ? null }:
{
preConfigure = "cp ${artefacts}/* .'';
outputs = [ "out" "artefacts" ];
}
Then you would nix-build to produce binaries and an artefacts directory.
Subsequent nix-builds would then use nix-build --arg 'artefacts'
'./results-artefacts'.
Handwaving, but hopefully that helps clarify.
ocharles
On Fri, Apr 22, 2016 at 5:35 PM stewart mackenzie <setori88 at gmail.com>
wrote:
> Interesting Oliver, though this sounds like it'll throw a recursive
> error. I'll investigate! cheers!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160422/a00a49d1/attachment-0001.html
More information about the nix-dev
mailing list