picnoir/nix-gh
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

fix "nix-build" examples

Browse source 
The existing "nix-build" examples were failing:

  error: cannot auto-call a function that has an argument without a default value (‘system’)

Thanks to @groxxda on irc for pointing out the fix!

Updated to completely remove unneeded path argument, suggested by @joachifm

Updated to remove other occurences of `all-packages.nix` from files as
suggested by @domenkozar

(cherry picked from commit 96d3534a9e)
This commit is contained in:
Scott R. Parish 2016-04-17 15:25:48 -07:00 committed by Eelco Dolstra
parent d39f51fa34
commit 0c67498be9
No known key found for this signature in database
GPG key ID: 8170B4726D7198DE
1 changed files with 8 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/manual/expressions/simple-building-testing.xml
View file

@ -7,15 +7,14 @@
<title>Building and Testing</title> <title>Building and Testing</title>
<para>You can now try to build Hello. Of course, you could do <para>You can now try to build Hello. Of course, you could do
<literal>nix-env -f pkgs/top-level/all-packages.nix -i hello</literal>, <literal>nix-env -i hello</literal>, but you may not want to install a
but you may not want to install a possibly broken package just yet. possibly broken package just yet. The best way to test the package is by
The best way to test the package is by using the command <command using the command <command linkend="sec-nix-build">nix-build</command>,
linkend="sec-nix-build">nix-build</command>, which builds a Nix which builds a Nix expression and creates a symlink named
expression and creates a symlink named <filename>result</filename> in <filename>result</filename> in the current directory:
the current directory:
<screen> <screen>
$ nix-build pkgs/top-level/all-packages.nix -A hello $ nix-build -A hello
building path `/nix/store/632d2b22514d...-hello-2.1.1' building path `/nix/store/632d2b22514d...-hello-2.1.1'
hello-2.1.1/ hello-2.1.1/
hello-2.1.1/intl/ hello-2.1.1/intl/
@ -29,8 +28,7 @@ $ ./result/bin/hello
Hello, world!</screen> Hello, world!</screen>
The <link linkend='opt-attr'><option>-A</option></link> option selects The <link linkend='opt-attr'><option>-A</option></link> option selects
the <literal>hello</literal> attribute from the <literal>hello</literal> attribute. This is faster than using the
<filename>all-packages.nix</filename>. This is faster than using the
symbolic package name specified by the <literal>name</literal> symbolic package name specified by the <literal>name</literal>
attribute (which also happens to be <literal>hello</literal>) and is attribute (which also happens to be <literal>hello</literal>) and is
unambiguous (there can be multiple packages with the symbolic name unambiguous (there can be multiple packages with the symbolic name
@ -69,7 +67,7 @@ block (or perform other derivations if available) until the build
finishes: finishes:
<screen> <screen>
$ nix-build pkgs/top-level/all-packages.nix -A hello $ nix-build -A hello
waiting for lock on `/nix/store/0h5b7hp8d4hqfrw8igvx97x1xawrjnac-hello-2.1.1x'</screen> waiting for lock on `/nix/store/0h5b7hp8d4hqfrw8igvx97x1xawrjnac-hello-2.1.1x'</screen>
So it is always safe to run multiple instances of Nix in parallel So it is always safe to run multiple instances of Nix in parallel