nixpkgs/doc/languages-frameworks/go.xml

161 lines
4.7 KiB
XML
Raw Normal View History

<section xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xml:id="sec-language-go">
2018-05-02 00:54:21 +01:00
<title>Go</title>
2018-05-02 00:54:21 +01:00
<para>
The function <varname>buildGoPackage</varname> builds standard Go programs.
</para>
2018-05-02 00:54:21 +01:00
<example xml:id='ex-buildGoPackage'>
<title>buildGoPackage</title>
<programlisting>
deis = buildGoPackage rec {
name = "deis-${version}";
version = "1.13.0";
goPackagePath = "github.com/deis/deis"; <co xml:id='ex-buildGoPackage-1' />
subPackages = [ "client" ]; <co xml:id='ex-buildGoPackage-2' />
src = fetchFromGitHub {
owner = "deis";
repo = "deis";
rev = "v${version}";
sha256 = "1qv9lxqx7m18029lj8cw3k7jngvxs4iciwrypdy0gd2nnghc68sw";
};
goDeps = ./deps.nix; <co xml:id='ex-buildGoPackage-3' />
buildFlags = "--tags release"; <co xml:id='ex-buildGoPackage-4' />
}
</programlisting>
2018-05-02 00:54:21 +01:00
</example>
<para>
<xref linkend='ex-buildGoPackage'/> is an example expression using
buildGoPackage, the following arguments are of special significance to the
function:
<calloutlist>
<callout arearefs='ex-buildGoPackage-1'>
<para>
2018-05-02 00:54:21 +01:00
<varname>goPackagePath</varname> specifies the package's canonical Go
import path.
</para>
2018-05-02 00:54:21 +01:00
</callout>
<callout arearefs='ex-buildGoPackage-2'>
<para>
2018-05-02 00:54:21 +01:00
<varname>subPackages</varname> limits the builder from building child
packages that have not been listed. If <varname>subPackages</varname> is
not specified, all child packages will be built.
</para>
<para>
2018-05-02 00:54:21 +01:00
In this example only <literal>github.com/deis/deis/client</literal> will
be built.
</para>
2018-05-02 00:54:21 +01:00
</callout>
<callout arearefs='ex-buildGoPackage-3'>
<para>
2018-05-02 00:54:21 +01:00
<varname>goDeps</varname> is where the Go dependencies of a Go program are
listed as a list of package source identified by Go import path. It could
be imported as a separate <varname>deps.nix</varname> file for
readability. The dependency data structure is described below.
</para>
2018-05-02 00:54:21 +01:00
</callout>
<callout arearefs='ex-buildGoPackage-4'>
<para>
2018-05-02 00:54:21 +01:00
<varname>buildFlags</varname> is a list of flags passed to the go build
command.
</para>
2018-05-02 00:54:21 +01:00
</callout>
</calloutlist>
</para>
<para>
The <varname>goDeps</varname> attribute can be imported from a separate
<varname>nix</varname> file that defines which Go libraries are needed and
should be included in <varname>GOPATH</varname> for
<varname>buildPhase</varname>.
</para>
<example xml:id='ex-goDeps'>
<title>deps.nix</title>
<programlisting>
[ <co xml:id='ex-goDeps-1' />
{
goPackagePath = "gopkg.in/yaml.v2"; <co xml:id='ex-goDeps-2' />
fetch = {
type = "git"; <co xml:id='ex-goDeps-3' />
url = "https://gopkg.in/yaml.v2";
rev = "a83829b6f1293c91addabc89d0571c246397bbf4";
sha256 = "1m4dsmk90sbi17571h6pld44zxz7jc4lrnl4f27dpd1l8g5xvjhh";
};
}
{
goPackagePath = "github.com/docopt/docopt-go";
fetch = {
type = "git";
url = "https://github.com/docopt/docopt-go";
rev = "784ddc588536785e7299f7272f39101f7faccc3f";
sha256 = "0wwz48jl9fvl1iknvn9dqr4gfy1qs03gxaikrxxp9gry6773v3sj";
};
}
]
</programlisting>
2018-05-02 00:54:21 +01:00
</example>
2018-05-02 00:54:21 +01:00
<para>
<calloutlist>
<callout arearefs='ex-goDeps-1'>
<para>
2018-05-02 00:54:21 +01:00
<varname>goDeps</varname> is a list of Go dependencies.
</para>
2018-05-02 00:54:21 +01:00
</callout>
<callout arearefs='ex-goDeps-2'>
<para>
2018-05-02 00:54:21 +01:00
<varname>goPackagePath</varname> specifies Go package import path.
</para>
2018-05-02 00:54:21 +01:00
</callout>
<callout arearefs='ex-goDeps-3'>
<para>
2018-05-02 00:54:21 +01:00
<varname>fetch type</varname> that needs to be used to get package source.
If <varname>git</varname> is used there should be <varname>url</varname>,
<varname>rev</varname> and <varname>sha256</varname> defined next to it.
</para>
2018-05-02 00:54:21 +01:00
</callout>
</calloutlist>
</para>
<para>
To extract dependency information from a Go package in automated way use
<link xlink:href="https://github.com/kamilchm/go2nix">go2nix</link>. It can
produce complete derivation and <varname>goDeps</varname> file for Go
programs.
</para>
<para>
<varname>buildGoPackage</varname> produces
<xref linkend='chap-multiple-output' xrefstyle="select: title" /> where
<varname>bin</varname> includes program binaries. You can test build a Go
binary as follows:
<screen>
$ nix-build -A deis.bin
</screen>
or build all outputs with:
2018-05-02 00:54:21 +01:00
<screen>
$ nix-build -A deis.all
</screen>
2018-05-02 00:54:21 +01:00
<varname>bin</varname> output will be installed by default with
<varname>nix-env -i</varname> or <varname>systemPackages</varname>.
</para>
2018-05-02 00:54:21 +01:00
<para>
You may use Go packages installed into the active Nix profiles by adding the
following to your ~/.bashrc:
<screen>
for p in $NIX_PROFILES; do
GOPATH="$p/share/go:$GOPATH"
done
</screen>
2018-05-02 00:54:21 +01:00
</para>
</section>