With CitC meaning all the source is instantly, "locally" available and up to date, and something like bazel.io meaning you always have a reliable and fast way to rebuild something out of cached/distributed build outputs[1], you don't need to distribute a binary in the general case.
Whoever needs a tool can cd to the source of the tool, build it right then and there, and run it.
Whoever needs a tool can cd to the source of the tool, build it right then and there, and run it.
[1] http://google-engtools.blogspot.com/2011/10/build-in-cloud-d...