Hi Oliver,
Here is a minimal example stripped of all the other crap:
https://github.com/fractalide/recompilation
Cheers!
/sjm
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
I'm afraid I don't really know what I'm looking at. Can you provide a
smaller self-contained example that I can look at?
On Sat, Apr 23, 2016 at 8:48 PM stewart mackenzie
wrote:
> Okay, I'm having a few problems implementing this, if you wouldn't
> mind taking a look at this
Okay, I'm having a few problems implementing this, if you wouldn't
mind taking a look at this please:
This is the package level default.nix which calls
`buildFractalideComponent`: http://nixpaste.lbr.uno/ZTwRzV0-?nix
Typically found here:
Oliver, what is in prelude/shell.nix? (nix-build -E '(import
prelude/shell.nix { nixpkgs = import /home/ollie/nixpkgs {}; }).dist')
/sjm
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
On 16-04-22 06:33pm, Oliver Charles wrote:
> It's certainly possible, because I just did it with Haskell ;)
>
> https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
Why do you need to put the atime two hours in the past?
Does cabal recompilation check for it in order to find out
A completely different approach would be to somehow break up your big
build into multiple derivations. This thread reminded me of nix-make:
https://github.com/edolstra/nix-make/blob/master/examples/not-so-simple-header-auto/default.nix
--Vladimir
smime.p7s
Description: S/MIME Cryptographic
On 04/22/2016 08:33 PM, Oliver Charles wrote:
> It's certainly possible, because I just did it with Haskell ;)
>
> https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
Hehe, the classic Haskell approach: make the impurity explicit in order
not to actually break purity...
This is a clever optimization. Thank you Oliver.
--
aycan
> On 22 Apr 2016, at 21:33, Oliver Charles wrote:
>
> It's certainly possible, because I just did it with Haskell ;)
>
> https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
>
>> On Fri, Apr 22,
You will save me hours of waiting in the future, definitely beer worthy!
Much appreciated Oliver!
On 23 Apr 2016 02:33, "Oliver Charles" wrote:
> It's certainly possible, because I just did it with Haskell ;)
>
>
It's certainly possible, because I just did it with Haskell ;)
https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
On Fri, Apr 22, 2016 at 7:16 PM stewart mackenzie
wrote:
> Yeah, I'm not so sure it's possible because one cannot copy from a
> precompiled
Yeah, I'm not so sure it's possible because one cannot copy from a
precompiled derivation output to a new derivation output, ie copy
cross derivation.
As these multiple outputs (outputs = [x y z]) are seen as different
derivations, this cannot happen right?
Have you actually managed to make
Ah, okay, I get your drift, I'll think how to make it succinct and
tidy in the code :-)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
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
Interesting Oliver, though this sounds like it'll throw a recursive
error. I'll investigate! cheers!
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Something I'm experimenting with here is to actually have these
intermediate artefacts be explicitly captured. I would use multiple outputs
to have both the normal complete binaries, and another output for .o files
and the like. Then you can feed this back in to future builds.
Does that help?
Hi,
I've got a bunch of artifacts being built in the
/tmp/nix-build-component_name.drv-0
now I want to point the build manager, in this case cargo using the
CARGO_TARGET_DIR env var to put the artifacts into a directory I make
directly in the /tmp/target_${name}
This way any further
You can set up a build environment resembling what nix-build would use
using the nix-shell command. All dependencies are provided, and each build
phase gets a function.
On 21 April 2016 at 17:42, stewart mackenzie wrote:
> Hi,
>
> I've got a bunch of artifacts being built in
17 matches
Mail list logo