On Sun, Jan 20, 2019 at 11:20 AM Tycho Andersen <ty...@tycho.ws> wrote:
> On Sun, Jan 20, 2019 at 11:18:38AM -0800, Jinwoo Lee 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. > > > > I would just do > > > > $ go build ./cmd/foo > > $ go build ./cmd/bar > > > > They create binaries in the current directory so you don't even have to > > copy them. > > That's how I have it now. The problem with this is that in the face of > modules, it re-writes the go.mod and go.sum files to not include the > deps of the binary it's not currently building, so you end up with a > bunch of unnecessary churn there. So it really does need to be in one > go command. > Sounds annoying. This seems like a good improvement to be made in the toolchain. > > Tycho > -- 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.
