On Fri, Jan 18, 2019 at 09:54:51PM -0500, Ian Denhardt wrote:
> You could just do:
>
> go build ./cmd/...
> cp ./cmd/foo/foo ./
> cp ./cmd/bar/bar ./
>
> ..and wrap it up in a script.
go build doesn't seem to produce binaries, though? In any case, Paul's
suggestion in a sibling mail works well e
Hello Chris,
I suspect you're trying to build a stateful server, which is highly discouraged
on GAE.
Scaling up and down to zero may kill instances any time, and you would lose
your scoreboard, if it's in memory or in the local fs. And what about 2
instances with contradictory scoreboards?
The s
As far i can see from all the previous answers i summarize this. let's see
at least if we share some points here:
- The *er convention is not better or worse than the *able convention,
the former may apply better in some scenarios than the latter.
- The "er" suffix goes like a charm with
My thought is that this ship has sailed long aGo.
Still, it is interesting how different terminology comes to be.
> On Jan 18, 2019, at 8:33 PM, Frank Dunn wrote:
>
> Readable is an adjective as in "This is a readable comment." Reader is a
> noun as in "Frank is a reader of comments." Read i
Perhaps the most idiomatic way of achieving this is:
GOBIN=$PWD go install ./cmd/{foo,bar}
go install is also more efficient than go build because it will only
perform the link step if the target is out of date.
I'm no expert with make, so I don't know how this sort of approach
maps back onto ma
