3 ms·
In my recent cross-platform projects, I just make a build.go script that can handle multiple commands and then just have builders only use that. E.g. go ru
by kodablah 9y ago
In my recent cross-platform projects, I just make a build.go script that can handle multiple commands and then just have builders only use that. E.g.
go run build.go build release
This crosses platforms, is easy to read and contribute to, is a much better language than make + CLI utils (or shell scripts), etc. It's not too much asking them to have "go" on the PATH. A similar approach could be taken w/ Python too. For most of this, there really isn't much code reuse needed, but it's often better to embed it than rely on external deps. Complex build script example: https://github.com/cretz/doogie/blob/8c53a266f35146a3c0d8f14fa22d830141f1497b/src/build.go https://github.com/cretz/doogie/blob/8c53a266f35146a3c0d8f14....
- 0xdeadbeefbabe 9y agocamlistore does this too, but a Makefile calls "go run make.go" https://github.com/camlistore/camlistore/blob/master/Makefile https://github.com/camlistore/camlistore/blob/master/Makefil...