Thank you!
go build -o . ./...
does the trick. And now I know what I'm looking for, I can find it in the
documentation:
*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
go build -o output_directory ./...
On Tuesday, June 30, 2020 at 12:58:05 PM UTC+2 b.ca...@pobox.com wrote:
> Suppose I have a tree of files like this, to build two executables:
>
> ==> ./go.mod <==
> module example.com/test
>
> go 1.14
>
> ==> ./shared.go <==
> package example
>
> const Answer =
