4 ms·
You would also need the tool chain if you're not on the same platform as built it originally, unless I just skimmed over it outputting multiple binaries and sel
by yjftsjthsd-h 8y ago
You would also need the tool chain if you're not on the same platform as built it originally, unless I just skimmed over it outputting multiple binaries and selecting them by local system type. Otherwise I clone a project on my Mac and it tries to run the binaries at the last developer built on her Raspberry Pi.
- prophesi 8y agoNo, it's pretty easy to set up cross-compilation with Go 1.5+. You'd just download the correct package for your OS. Luckily for you, the project already has binaries built for Mac (Darwin): https://github.com/git-hooks/git-hooks/releases https://github.com/git-hooks/git-hooks/releases
- yjftsjthsd-h 8y agoOh, I misunderstood; I thought you were shipping binaries in the git rep to be run as hooks, not that git-hooks itself was written in Go. If it's the git-hooks itself then yeah portability should be good. I do notice that you're only releasing binaries for Darwin and Linux; no love for the BSDs? Not that it's a big deal, since most Go stuff is trivial to build on any supported platform.