No Silver-Go-Bullet. Yet another ad-hoc build.
I was doing a small Go command line tool project. All the time I was starting Go codebase, I looking for the proper way to setup project and to build it.
The right build to me is the build which is reproducible. Such build is likely to be isolated from a machine where you run it. Be it Linux, Mac or Windows. Also, the right build should have all dependencies fixed. Otherwise, we have merely no chances to recreated it in the future.
As the very first example, I decided to use the approach from Consul Template.
That time (May 2017) it was a
make based build which was using the official Docker container to run.
It was great! I was able to kick-start the project and to focus on development. But, it was crazy slow.
It took seconds to compile a tiny project. It was also unable to run on Windows.
I did research. Found several approaches to building Go with Gradle. I decided to try Gogradle. Also, there is gradle-golang-plugin. Overall, the story did not play well because some issues I came across. And again, the solution was heavy!
Isolation. Docker. Cool stuff. But, the best stuff, it to think Docker, and event avoid it. The Go itself is amazing in that sense. The go binaries have zero dependencies. And this means we are able to zero-copy dependencies.
Finally, I created the following script. A still waiting for something better, and easier to use.
The script downloads Go binaries for Mac or Linux to a build folder. It does not update the folder if there is Go already.
You may find the actual version on GitHub. https://github.com/jonnyzzz/go-build-script And let me know if you know the better way to Go.comments powered by Disqus