On Sun, Jan 20, 2019 at 11:33 AM Jan Mercl <0xj...@gmail.com> wrote:
>
>
>
> On Sun, Jan 20, 2019 at 8:22 PM Jinwoo Lee <jinwo...@gmail.com> wrote:
>
> > It looks like "go build ./cmd/..." works when there's only one directory
> under cmd. When there are multiple directories there, the command doesn't
> generate any binaries for me.
>
> It works on all sub directories. But `go build` puts the binary locally,
> while `go install cmd/...` should put all the binaries on $GOBIN or
> $GOPATH/bin if $GOBIN is not set.
>
Did you try? That's not the behavior I'm seeing. When there's multiple
directories under cmd, 'go build ./cmd/...' doesn't create any binaries --
either in the current directory or in ./cmd/{foo,bar}. It does seem to do
something and emits build errors if any, but no binaries. It does work when
there's only one directory, e.g. ./cmd/foo.
>
>
> --
>
> -j
>
--
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 golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
