Thank you!

go build -o . ./...

does the trick.  And now I know what I'm looking for, I can find it in the 

*When compiling multiple packages or a single non-main package, build 
compiles the packages but discards the resulting object, serving only as a 
check that the packages can be built.*

*The -o flag forces build to write the resulting executable or object to 
the named output file or directory, instead of the default behavior 
described in the last two paragraphs.*

Thanks again,


You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit

Reply via email to