Go now comes with support for all architectures built in.

Things have been much better since v1.5 of Go was released. Pre 1.5īefore 1.5, cross compilation was an arduous process, requiring massive scripts to build separate go compilers for each supported platform. How do you use one system to compile binaries that will work on the other? This is called cross-compiling, and it’s pretty simple with Go. However, many developers use OS X or Windows on their local machine, and another OS like Linux on others. This is great for Unix administrators or DevOps engineers, as they can send their tools with them when they work on remote systems. Since Go is a statically compiled language, it’s well designed for producing tiny, pre-compiled tools. You may want to check the osxcross requirements as well if you’re having problems.How do I compile a binary designed to run on a different platform than my local host? I don’t think the version requirements are too strict for the packages listed below. There are a few system dependencies required to work with osxcross. This process should work for other macOS versions, but is untested. The only device I have to test on at time of writing is a Macbook Air with macOS Mojave on it. I’ve also tested this process in CircleCI and it seems to be working fine. Linux Mint 19.1, Dell XPS1 15, Intel i9 圆4.This process should work in any modern-ish Debian-based environment. Hopefully it spares you a weekend of your own pain. A weekend of pain later, and I have the following post. This is naturally a bit crap, so I set out to find a Linux-only solution to cross compile for macOS using osxcross.

I use Linux Mint nearly all the time, so building for macOS targets has required asking very nicely to borrow a spare Macbook Air. I’ve recently been working on a Rust project at work which requires compiling for Linux (GNU), Linux (musl - for Alpine Linux) and macOS.

Cross compile for mac on linux