[Nix-dev] About using clang+llvm as default 'stdenv' compiler

[Max Ivanov]

1. Use pkgs.clangStdenv instead of pkgs.stdenv
2. You'll have different hashes in /nix/store and it is up to you
which one to link to your profile. You can create 2 profiles one for
each firefox flavor.


On Thu, Apr 24, 2014 at 12:17 AM, Anderson Torres
<torres.anderson.85 at gmail.com> wrote:
> Hello, Nixers!
>
> I was thinking about a thing here.
>
> 1 - How can I set a new C compiler for stdenv? I want to use llvm+clang as
> default compiler toolchain when running nix-build, etc. (Yes, I like some
> masochistic testing...)
>
> 2 - Using a different compiler certainly affect the object code produced -
> and in NIX it is propagated through the /nix/store tree as a different hash.
> But, technically, both compilers would produce 'equivalent' object codes.
>
> The default toolchain is gcc, but my local chain is clang+llvm. So, can I
> use at the same time a, say, Firefox compiled by Hydra and updated on the
> unstable channels, and a local, 'clang7ed' version of Firefox?
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>