Homebrew package manager formula to install cross-compiler toolchains targeting Linux boxes.
The default installation contains toolchains for x86 64-bit Linux (x86_64-linux-musl). Others can be installed with package options (see brew info).
Note, when using the toolchain, the generated binaries will only run on a system with musl libc installed. Either musl-based distributions like Alpine Linux or distributions having musl libc installed as separate packages (e.g., Debian/Ubuntu).
Binaries statically linked with musl libc (linked with -static) have no external dependencies, even for features like DNS lookups or character set conversions that are implemented with dynamic loading on glibc. The application can be deployed as a single binary file and run on any device with the appropriate ISA and Linux kernel or Linux syscall ABI emulation layer including bare docker containers.
Tool Versions:
Partially based on:
Depends on jthat/musl-cross-make to do the heavy lifting, which is in turn based on richfelker/musl-cross-make and the clang branch of apexrtos/musl-cross-make.
- Install with Homebrew:
$ brew tap jthat/musl-cross
- To use GCC:
$ brew install musl-cross-gcc
- To use Clang:
$ brew install musl-cross-clang
-
For dynamically linked applications, ensure the correct version of
muslis installed on the target device. -
Compile with
<TARGET>-cce.g.,x86_64-linux-musl-cc, deploy, and run.
i686-linux-muslx86_64-linux-muslx86_64-linux-muslx32arm-linux-musleabiarm-linux-musleabihfaarch64-linux-muslmips-linux-muslmips64-linux-muslpowerpc-linux-muslpowerpc64-linux-musls390x-linux-musl
Other targets or variants can be added easily by extending the hash OPTION_TARGET_MAP in the formula as long as musl-cross-make and musl libc also support them.