1
0
mirror of https://github.com/golang/go synced 2024-11-20 03:24:41 -07:00

cmd/go: mention that _test.go files are ignored when building

Fixes #15315

Change-Id: I8fea31507a5f83df8a86fb067f1b11d90133dc09
Reviewed-on: https://go-review.googlesource.com/22180
Reviewed-by: Chris Broadfoot <cbro@golang.org>
This commit is contained in:
Andrew Gerrand 2016-04-18 13:31:50 +10:00
parent 6ec481b06c
commit 135572eb32
2 changed files with 4 additions and 0 deletions

View File

@ -69,6 +69,8 @@ When compiling multiple packages or a single non-main package,
build compiles the packages but discards the resulting object, build compiles the packages but discards the resulting object,
serving only as a check that the packages can be built. serving only as a check that the packages can be built.
When compiling packages, build ignores files that end in '_test.go'.
The -o flag, only allowed when compiling a single package, The -o flag, only allowed when compiling a single package,
forces build to write the resulting executable or object forces build to write the resulting executable or object
to the named output file, instead of the default behavior described to the named output file, instead of the default behavior described

View File

@ -48,6 +48,8 @@ When compiling multiple packages or a single non-main package,
build compiles the packages but discards the resulting object, build compiles the packages but discards the resulting object,
serving only as a check that the packages can be built. serving only as a check that the packages can be built.
When compiling packages, build ignores files that end in '_test.go'.
The -o flag, only allowed when compiling a single package, The -o flag, only allowed when compiling a single package,
forces build to write the resulting executable or object forces build to write the resulting executable or object
to the named output file, instead of the default behavior described to the named output file, instead of the default behavior described