Home  >  Article  >  Backend Development  >  What is the use of go clean?

What is the use of go clean?

青灯夜游
青灯夜游Original
2023-01-28 11:28:131561browse

In the Go language, the "go clean" command is used to remove files compiled and generated in the current source code package and associated source code packages. The removed files can be: 1. An executable file with the same name as the package name or source code file generated in the current directory when executing the "go build" command; 2. When executing the "go test" command and adding the "-c" flag A file generated in the current directory with the package name plus ".test" suffix; 3. The result file generated when executing the "go install" command to install the current code package, etc.

What is the use of go clean?

The operating environment of this tutorial: Windows 10 system, GO version 1.18, Dell G3 computer.

The go clean command in Go language can remove the compiled and generated files in the current source code package and associated source code packages. These files include the following:

  • The executable file with the same name as the package name or Go source file is generated in the current directory when the go build command is executed. Under Windows, it is a file with the same name as the package name or Go source code file and with the ".exe" suffix.

  • The package name generated in the current directory when executing the

    go test command and adding the -c tag is named after the package name plus the ".test" suffix. document. Under Windows, it is a file with the package name plus ".test.exe" suffix.

  • The result file generated when executing the

    go install command to install the current code package. If the current code package only contains library source files, the result file refers to the corresponding archive file in the pkg directory of the workspace. If the current code package contains only one command source code file, the result file refers to the executable file in the bin directory of the workspace.

  • Files or directories left in the corresponding directory when compiling Go or C source code files. Includes: "_obj" and "_test" directories, files named "_testmain.go", "test.out", "build.out" or "a.out", named with ".5", ".6" , ".8", ".a", ".o" or ".so" as the suffix. These directories and files are generated in the temporary directory when executing the

    go build command.

go cleanThe command can also specify some parameters. The meaning of the corresponding parameters is as follows:

  • -i Clear the associated installed packages and executable files, that is, through go installInstalled files;

  • -n Print out the cleanup command that needs to be executed, but do not execute it, so that you can easily know how the bottom layer is running. ;

  • -r Circular clearing of packages introduced in import;

  • -x prints out the detailed command executed, which is actually the execution version printed by -n;

  • -cache deletes all go buildCommand cache

  • -testcache Delete all test results of the current package

Generally, the

go clean command is used to clear the compiled files, and then the source code is submitted to github to facilitate the management of the source code.

Let’s take a local project as an example to demonstrate the go clean command:

go clean -n
cd D:\code
rm -f code code.exe code.test code.test.exe main main.exe

Using the -n flag in the command can print out the execution process of the command, but it will not actually implement. If you want to print the execution process of the command and execute the command at the same time, you can use the -x flag, as shown below:

go clean -x
cd D:\code
rm -f code code.exe code.test code.test.exe main main.exe

What is the use of go clean?Figure: Comparison before and after running the go clean command

[Related recommendations:

Go video tutorial, Programming teaching]

The above is the detailed content of What is the use of go clean?. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn