First,// + build will gradually replace// go: build. Both annotations can be used in go version 1.16-1.18 as the transition period. See official website https://www.jetbrains.com/help/go/configuring-build-constraints-and-vendoring.html
However,// + build cannot be used in versions below 1.16. If it is used, an error will be reported: Golan — build constraints exclude all go files.
1.16 the following versions should use// go: build
And make the following settings
Read More:
- Error report of GoLand project after go reloading Error:cannot find The solution of package error
- Grep finds all files containing a string in Linux
- Brief introduction of cmake generating all in vs Project_ BUILD、INSTALL、ZERO_ Check function!!
- Linux shell RM deletes all. O suffix files in the subdirectory
- The template tags of all vscode Vue files report errors in red~
- Error: Projects must list all files or use an ‘include‘ pattern.
- Solve the problem that M1 Mac can’t debug when using GoLand
- The use of makefile in GoLand under Windows
- Module build failed Error Plugin/Preset files are not allowed to export objects, only functions (How to Fix)
- Java – read all the files and folders in a certain directory and three methods to get the file name from the file path
- Go get github.com/kotakanbe/go -Problems encountered in CVE dictionary Download
- Line wrap of GoLand code
- NPM run build failed to package err! Missing script: build
- GoLand：Unresolved reference ‘NewFunction‘
- Error: Rule can only have one resource source (provided resource and test + include + exclude)
- failed to find Build Tools revision 23.0.2 Install Build Tools 23.0.2 and sync project
- Go run error go run: cannot run non main package
- The too many open files solution appears in stream classes such as files.list
- Ida batch processes virus share samples to obtain ASM files and bytes files
- standard_init_linux.go:178: exec user process caused “no such file or directory”