Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

go-clean(1) [bsd man page]

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

NAME
go - tool for managing Go source code SYNOPSIS
go clean [-i] [-r] [-n] [-x] [ packages ] DESCRIPTION
Clean removes object files from package source directories. The go command builds most objects in a temporary directory, so go clean is mainly concerned with object files left by other tools or by manual invocations of go build. Specifically, clean removes the following files from each of the source directories corresponding to the import paths: _obj/ old object directory, left from Makefiles _test/ old test directory, left from Makefiles _testmain.go old gotest file, left from Makefiles test.out old test log, left from Makefiles build.out old test log, left from Makefiles *.[568ao] object files, left from Makefiles DIR(.exe) from go build DIR.test(.exe) from go test -c MAINFILE(.exe) from go build MAINFILE.go In the list, DIR represents the final path element of the directory, and MAINFILE is the base name of any Go source file in the directory that is not included when building the package. OPTIONS
-i The -i flag causes clean to remove the corresponding installed archive or binary (what 'go install' would create). -n The -n flag causes clean to print the remove commands it would execute, but not run them. -r The -r flag causes clean to be applied recursively to all the dependencies of the packages named by the import paths. -x The -x flag causes clean to print remove commands as it executes them. For more about specifying packages, see go-packages(7). 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-CLEAN(1)

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