cmd/go: docs to make it more obvious how build tags are meant to be passed #18351
Labels
FrozenDueToAge
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.7.3 darwin/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Volumes/dev/gpuroot"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.3/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.3/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/kp/m9dnkfhx4r9_8dv1cns7m0gh00bkfl/T/go-build113285281=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
Looked for instructions online.
What did you expect to see?
The same page to contain information about specifying build constraints, and how to pass those via the go tool.
Information on how to pass multiple flags i.e. separated by spaces?
What did you see instead?
I had to look through source code and tests to find out how multiple tags were passed. The official docs are scarce.
Space-separated tags seems a bit error-prone. If commas are not allowed in tag names, would it be possible to support commas as well?
The text was updated successfully, but these errors were encountered: