Using GB as my every day build tool

This is a creation in Article, where the information may have evolved or changed.

For the longest time I had this alias in my.bashrc

Alias gb= ' Go install-v '

As an homage to John Asmuth's GB tool which I was very fond of the by-back before we had the go tool.

Once GB is written, I had to remove this alias and live in a world where I used the Go tool and GB concurrently. Now, with the improvements that has landed since Gophercon I ' ve decided it's time to get serious about eating my own dog Food and use GB as a full time replacement for the Go tool.

I use GB for just to build GB projects, and to work on Juju, my $DAYJOB, as well as using GB to develop GB itself. Because the definition of a GB project is backwards compatible with $GOPATH I don ' t even need to rewrite every Go package I Want to work on as a GB project, I can work with them with their source happily in my $GOPATH.

GB isn ' t perfect yet, there is still some major missing pieces. I hope by aggressively dogfooding I'll be able to close the gaps before the end of the year. Specifically:

• GB build works well, and the GB test story was less solid; I hope to reach parity with go test on the next few months by adding support for test flags,-race and coverage options.
• Support for cross compilation were always high on my list, and are being actively worked on, and would be available to Experi ment within the next weeks. At the this point I envisage it'll be go 1.5 only, go 1.4 support may come in time, and is not a high priority.

If others want to join me and do GB their default Go build tool, I ' d welcome the company, and of course, your bugs report S.

Related Posts:

1. GB, a project based build tool for the Go programming language
2. Introducing GB, a project based build tool for the Go programming language
3. What does go build build?
4. Using go test, build and install