Lines Matching refs:package

9 [[golang-package-tutorial]]
11 ==== +golang-package+ tutorial
13 First, let's see how to write a +.mk+ file for a go package,
28 12: $(eval $(golang-package))
31 On line 7, we declare the version of the package.
33 On line 8, we declare the upstream location of the package, here
37 On line 9 and 10, we give licensing details about the package.
39 Finally, on line 12, we invoke the +golang-package+ macro that
40 generates all the Makefile rules that actually allow the package to be
43 [[golang-package-reference]]
45 ==== +golang-package+ reference
47 In their +Config.in+ file, packages using the +golang-package+
51 If you need CGO support in your package, you must add a dependency on
54 The main macro of the Go package infrastructure is
55 +golang-package+. It is similar to the +generic-package+ macro. The
57 +host-golang-package+ macro.
58 Host packages built by +host-golang-package+ macro should depend on
62 by defining a number of variables before calling the +golang-package+.
64 All the package metadata information variables that exist in the
65 xref:generic-package-reference[generic package infrastructure] also
71 +FOO_DEPENDENCIES+ variable of a package, since this basic dependency
72 is automatically added as needed by the Go package infrastructure.
75 optionally be defined, depending on the package's needs. Many of them
79 * The package must specify its Go module name in the +FOO_GOMOD+
82   take the value +github.com/bar/foo+ for a package that specifies
83   +FOO_SITE = $(call github,bar,foo,$(FOO_VERSION))+. The Go package
85   in the package source tree if it doesn't exist.
95    will be produced, and that by default we name it after the package
108   name of package.
119   infrastructure is used, if the package +.mk+ file defines its own