Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

go-packages(7) [bsd man page]

GO-PACKAGES(7)						 Miscellaneous Information Manual					    GO-PACKAGES(7)

NAME

       go - tool for managing Go source code

DESCRIPTION

       Many commands apply to a set of packages:

	     go action [packages]

       Usually, [packages] is a list of import paths.

       An  import path that is a rooted path or that begins with a . or .. element is interpreted as a file system path and denotes the package in
       that directory.

       Otherwise, the import path P denotes the package found in the directory DIR/src/P for some DIR listed in the  GOPATH  environment  variable
       (see 'go help gopath').

       If no import paths are given, the action applies to the package in the current directory.

       The  special  import path "all" expands to all package directories found in all the GOPATH trees.  For example, 'go list all' lists all the
       packages on the local system.

       The special import path "std" is like all but expands to just the packages in the standard Go library.

       An import path is a pattern if it includes one or more "..." wildcards, each of which can match any string, including the empty string  and
       strings	containing slashes.  Such a pattern expands to all package directories found in the GOPATH trees with names matching the patterns.
       As a special case, x/... matches x as well as x's subdirectories.  For example, net/... expands to net and packages in its subdirectories.

       An import path can also name a package to be downloaded from a remote repository.  Run 'go help remote' for details.

       Every package in a program must have a unique import path.  By convention, this is arranged by starting each path with a unique prefix that
       belongs	to  you.   For example, paths used internally at Google all begin with 'google', and paths denoting remote repositories begin with
       the path to the code, such as 'code.google.com/p/project'.

       As a special case, if the package list is a list of .go files from a single directory, the command is applied to a single synthesized pack-
       age made up of exactly those files, ignoring any build constraints in those files and ignoring any other files in the directory.

AUTHOR

       This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).

								    2012-05-13							    GO-PACKAGES(7)

Check Out this Related Man Page

GO-BUILD(1)						      General Commands Manual						       GO-BUILD(1)

NAME

       go - tool for managing Go source code

SYNOPSIS

       go build [-o output] [ build flags ] [ packages ]

DESCRIPTION

       Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results.

       If the arguments are a list of .go files, build treats them as a list of source files specifying a single package.

       When the command line specifies a single main package, build writes the resulting executable to output.	Otherwise build compiles the pack-
       ages but discards the results, serving only as a check that the packages can be built.

       The -o flag specifies the output file name.  If not specified, the name is packagename.a (for a non-main package) or the base name  of  the
       first source file (for a main package).

OPTIONS

       The build flags are shared by the build, install, run, and test commands:

       -a     force rebuilding of packages that are already up-to-date.

       -n     print the commands but do not run them.

       -p n   the number of builds that can be run in parallel. The default is the number of CPUs available.

       -v     print the names of packages as they are compiled.

       -work  print the name of the temporary work directory and do not delete it when exiting.

       -x     print the commands.

       -compiler name
	      name of compiler to use, as in runtime.Compiler (gccgo or gc)

       -gccgoflags 'arg list'
	      arguments to pass on each gccgo compiler/linker invocation

       -gcflags 'arg list'
	      arguments to pass on each 5g, 6g, or 8g compiler invocation

       -ldflags 'flag list'
	      arguments to pass on each 5l, 6l, or 8l linker invocation

       -tags 'tag list'
	      a  list  of  build tags to consider satisfied during the build.  See the documentation for the go/build package for more information
	      about build tags.

       For more about specifying packages, see go-packages(7).

       For more about where packages and binaries are installed, see go-gopath(1).

SEE ALSO

       go-install(1), go-get(1), go-clean(1).

AUTHOR

       This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).

								    2012-05-13							       GO-BUILD(1)
Man Page