diff options
| author | John Ericson <John.Ericson@Obsidian.Systems> | 2018-01-25 18:32:18 -0500 |
|---|---|---|
| committer | John Ericson <John.Ericson@Obsidian.Systems> | 2018-01-26 12:33:14 -0500 |
| commit | e316ba1fc48bfb4d2b8013a2bcdc54d63e8e6e0e (patch) | |
| tree | c5dfc77110ce371580d0c7411e1fe33e433e590d /doc/cross-compilation.xml | |
| parent | 931a0b8be80661902baefb3e7d55403be893e0e6 (diff) | |
doc: chap cross: Make example command stick out more
It should be in a <programlisting>, not <command>, tag.
Diffstat (limited to 'doc/cross-compilation.xml')
| -rw-r--r-- | doc/cross-compilation.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/cross-compilation.xml b/doc/cross-compilation.xml index 028fd6744910b..3e67944e58f79 100644 --- a/doc/cross-compilation.xml +++ b/doc/cross-compilation.xml @@ -253,7 +253,8 @@ or also with <varname>crossSystem</varname>, in which case packages run on the latter, but all building happens on the former. Both parameters take the same schema as the 3 (build, host, and target) platforms defined in the previous section. As mentioned above, <literal>lib.systems.examples</literal> has some platforms which are used as arguments for these parameters in practice. - You can use them programmatically, or on the command line like <command>nix-build <nixpkgs> --arg crossSystem '(import <nixpkgs/lib>).systems.examples.fooBarBaz'</command>. + You can use them programmatically, or on the command line: <programlisting> +nix-build <nixpkgs> --arg crossSystem '(import <nixpkgs/lib>).systems.examples.fooBarBaz' -A whatever</programlisting> </para> <para> While one is free to pass both parameters in full, there's a lot of logic to fill in missing fields. |