diff options
author | John Ericson <John.Ericson@Obsidian.Systems> | 2017-07-07 13:24:33 -0400 |
---|---|---|
committer | John Ericson <John.Ericson@Obsidian.Systems> | 2017-07-07 13:24:33 -0400 |
commit | 9dc2a3aeba864f0fd989e50344500a94df0efc1f (patch) | |
tree | be6fe1adeba83fd875b1d3f4447cefa51c0039c1 /doc/cross-compilation.xml | |
parent | a302d7360f201cc4fcfb4a43a432b31536795507 (diff) |
doc: Update cross compilation chapter for stdenv.{build,host,target}Platform
Diffstat (limited to 'doc/cross-compilation.xml')
-rw-r--r-- | doc/cross-compilation.xml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/cross-compilation.xml b/doc/cross-compilation.xml index 650db718665ca..77d020afa2df3 100644 --- a/doc/cross-compilation.xml +++ b/doc/cross-compilation.xml @@ -37,8 +37,9 @@ </para> <para> In Nixpkgs, these three platforms are defined as attribute sets under the names <literal>buildPlatform</literal>, <literal>hostPlatform</literal>, and <literal>targetPlatform</literal>. - All three are always defined at the top level, so one can get at them just like a dependency in a function that is imported with <literal>callPackage</literal>: - <programlisting>{ stdenv, buildPlatform, hostPlatform, fooDep, barDep, .. }: ...</programlisting> + All three are always defined as attributes in the standard environment, and at the top level. That means one can get at them just like a dependency in a function that is imported with <literal>callPackage</literal>: + <programlisting>{ stdenv, buildPlatform, hostPlatform, fooDep, barDep, .. }: ...buildPlatform...</programlisting>, or just off <varname>stdenv</varname>: + <programlisting>{ stdenv, fooDep, barDep, .. }: ...stdenv.buildPlatform...</programlisting>. </para> <variablelist> <varlistentry> |