“Zero setup” cross compilation and “cross testing” of Rust crates
This project is developed and maintained by the cross-rs team. It was previously maintained by the Rust Embedded Working Group Tools team. New contributors are welcome! Please join our Matrix room and say hi.
`cross test`ing a crate for the aarch64-unknown-linux-gnu target
-
crosswill provide all the ingredients needed for cross compilation without touching your system installation. -
crossprovides an environment, cross toolchain and cross compiled libraries, that produces the most portable binaries. -
“cross testing”,
crosscan test crates for architectures other than i686 and x86_64. -
The stable, beta and nightly channels are supported.
See our Getting Started guide for detailed installation instructions.
-
A Linux kernel with binfmt_misc support is required for cross testing.
One of these container engines is required. If both are installed, cross will
default to docker.
- Docker. Note that on Linux non-sudo users need to be in the
dockergroup or use rootless docker. Read the container engine install guide for the required installation and post-installation steps. Requires version 20.10 (API 1.40) or later.
- Podman. Requires version 3.4.0 or later.
cargo install cross --git https://github.com/cross-rs/crossIt's also possible to directly download the pre-compiled release binaries or using cargo-binstall.
cross has the exact same CLI as Cargo
but relies on Docker or Podman. For Docker, you'll have to start
the daemon before you can use it.
# (ONCE PER BOOT, on Linux)
# Start the Docker daemon, if it's not already running using systemd
# on WSL2 and other systems using SysVinit, use `sudo service docker start`.
$ sudo systemctl start docker
# MAGIC! This Just Works
$ cross build --target aarch64-unknown-linux-gnu
# EVEN MORE MAGICAL! This also Just Works
$ cross test --target mips64-unknown-linux-gnuabi64
# Obviously, this also Just Works
$ cross rustc --target powerpc-unknown-linux-gnu --release -- -C lto
Additional documentation can be found on the wiki.
You have three options to configure cross. All of these options use the TOML format for configuration and the possible configuration values are documented here.
You can directly set configuration values in your Cargo.toml file, under the [package.metadata.cross] table, i.e. key prefix.
An example config snippet would look like this:
[package.metadata.cross.target.aarch64-unknown-linux-gnu]
xargo = false
image = "test-image"
runner = "custom-runner"You can put your configuration inside a Cross.toml file in your project root directory.
By setting the CROSS_CONFIG environment variable, you can tell cross where it should search for the config file. This way you are not limited to a Cross.toml file in the project root.
cross provides default Docker images for the targets listed below. However, it
can't cover every single use case out there. For other targets, or when the
default image is not enough, you can use the target.{{TARGET}}.image field in
Cross.toml to use custom Docker image for a specific target:
[target.aarch64-unknown-linux-gnu]
image = "my/image:tag"In the example above, cross will use a image named my/image:tag instead of
the default one. Normal Docker behavior applies, so:
-
Docker will first look for a local image named
my/image:tag -
If it doesn't find a local image, then it will look in Docker Hub.
-
If only
image:tagis specified, then Docker won't look in Docker Hub. -
If only
tagis omitted, then Docker will use thelatesttag.
If you're using a custom Dockerfile, you can use target.{{TARGET}}.dockerfile to automatically build it
[target.aarch64-unknown-linux-gnu]
dockerfile = "./path/to/where/the/Dockerfile/resides"cross will build and use the image that was built instead of the default image.
It's recommended to base your custom image on the default Docker image that
cross uses: ghcr.io/cross-rs/{{TARGET}}:{{VERSION}} (where {{VERSION}} is cross's version).
This way you won't have to figure out how to install a cross C toolchain in your
custom image.
FROM ghcr.io/cross-rs/aarch64-unknown-linux-gnu:latest
RUN dpkg --add-architecture arm64 && \
apt-get update && \
apt-get install --assume-yes libfoo:arm64If you want cross to provide the FROM instruction, you can do the following
ARG CROSS_BASE_IMAGE
FROM $CROSS_BASE_IMAGE
RUN ...cross enables you to add dependencies and run other necessary commands in the image before using it.
This action will be added to the used image, so it won't be ran/built every time you use cross.
[target.aarch64-unknown-linux-gnu]
pre-build = ["dpkg --add-architecture arm64 && apt-get update && apt-get install --assume-yes libfoo:arm64"]When running cross from inside a container, cross needs access to
the hosts docker daemon itself. This is normally achieved by mounting the
docker daemons socket /var/run/docker.sock. For example:
$ docker run -v /var/run/docker.sock:/var/run/docker.sock -v .:/project \
-w /project my/development-image:tag cross build --target mips64-unknown-linux-gnuabi64
The image running cross requires the rust development tools to be installed.
With this setup cross must find and mount the correct host paths into the
container used for cross compilation. This includes the original project directory as
well as the root path of the parent container to give access to the rust build
tools.
To inform cross that it is running inside a container set CROSS_CONTAINER_IN_CONTAINER=true.
A development or CI container can be created like this:
FROM rust:1
# set CROSS_CONTAINER_IN_CONTAINER to inform `cross` that it is executed from within a container
ENV CROSS_CONTAINER_IN_CONTAINER=true
# install `cross`
RUN cargo install cross
...
Limitations: Finding the mount point for the containers root directory is currently only available for the overlayfs2 storage driver. In order to access the parent containers rust setup, the child container mounts the parents overlayfs. The parent must not be stopped before the child container, as the overlayfs can not be unmounted correctly by Docker if the child container still accesses it.
By default, cross tries to use Docker or Podman, in that order.
If you want to choose a container engine explicitly, you can set the
binary name (or path) using the CROSS_CONTAINER_ENGINE
environment variable.
For example in case you want use Podman, you can set CROSS_CONTAINER_ENGINE=podman.
By default, cross does not pass most environment variables into the build environment from the calling shell. This is chosen as a safe default as most use cases will not want the calling environment leaking into the inner execution environment. There are, however, some notable exceptions: most environment variables cross or cargo reads are passed through automatically to the build environment.
In the instances that you do want to pass through environment variables, this
can be done via build.env.passthrough in your Cross.toml:
[build.env]
passthrough = [
"RUST_BACKTRACE",
"RUST_LOG",
"TRAVIS",
]To pass variables through for one target but not others, you can use this syntax instead:
[target.aarch64-unknown-linux-gnu.env]
passthrough = [
"RUST_DEBUG",
]For more detailed documentation on which environment variables are automatically passed to the build environment, see Environment Variable Passthrough on our wiki.
Certain unstable features can enable additional functionality useful to cross-compiling. Note that these are unstable, and may be removed at any time (particularly if the feature is stabilized or removed), and will only be used on a nightly channel.
CROSS_UNSTABLE_ENABLE_DOCTESTS=true: also run doctests.
In addition to passing environment variables, you can also specify environment variables pointing to paths which should be mounted into the container:
[target.aarch64-unknown-linux-gnu.env]
volumes = [
"BUILD_DIR",
]By default, cross uses xargo to build your Cargo project only for all
non-standard targets (i.e. something not reported by rustc/rustup). However,
you can use the build.xargo or target.{{TARGET}}.xargo field in
Cross.toml to force the use of xargo:
# all the targets will use `xargo`
[build]
xargo = trueOr,
# only this target will use `xargo`
[target.aarch64-unknown-linux-gnu]
xargo = truexargo = false will work the opposite way (pick cargo always) and is useful
when building for custom targets that you know to work with cargo.
A target is considered as “supported” if cross can cross compile a
“non-trivial” (binary) crate, usually Cargo, for that target.
Testing support (cross test) is more complicated. It relies on QEMU
emulation, so testing may fail due to QEMU bugs rather than bugs in your crate.
That said, a target has a ✓ in test column of the table below if it can run
the compiler-builtins test suite.
Also, testing is very slow. cross test runs units tests sequentially because
QEMU gets upset when you spawn multiple threads. This means that, if one of your
unit tests spawns threads, then it's more likely to fail or, worst, never
terminate.
| Target | libc | GCC | C++ | QEMU | test |
|---|---|---|---|---|---|
aarch64-linux-android [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
aarch64-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
aarch64-unknown-linux-gnu:centos [7] |
2.17 | 4.8.5 | 4.2.1 | ✓ | |
aarch64-unknown-linux-musl |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
arm-linux-androideabi [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
arm-unknown-linux-gnueabi |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
arm-unknown-linux-gnueabihf |
2.31 | 8.5.0 | ✓ | 6.1.0 | ✓ |
arm-unknown-linux-musleabi |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
arm-unknown-linux-musleabihf |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
armv5te-unknown-linux-gnueabi |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
armv5te-unknown-linux-musleabi |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
armv7-linux-androideabi [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
armv7-unknown-linux-gnueabi |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
armv7-unknown-linux-gnueabihf |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
armv7-unknown-linux-musleabi |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
armv7-unknown-linux-musleabihf |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
i586-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | N/A | ✓ |
i586-unknown-linux-musl |
1.1.24 | 9.2.0 | ✓ | N/A | ✓ |
i686-unknown-freebsd |
1.5 | 6.4.0 | ✓ | N/A | |
i686-linux-android [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
i686-pc-windows-gnu |
N/A | 9.4 | ✓ | N/A | ✓ |
i686-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
mips-unknown-linux-gnu |
2.30 | 9.4.0 | ✓ | 6.1.0 | ✓ |
mips-unknown-linux-musl |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
mips64-unknown-linux-gnuabi64 |
2.30 | 9.4.0 | ✓ | 6.1.0 | ✓ |
mips64-unknown-linux-muslabi64 |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
mips64el-unknown-linux-gnuabi64 |
2.30 | 9.4.0 | ✓ | 6.1.0 | ✓ |
mips64el-unknown-linux-muslabi64 |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
mipsel-unknown-linux-gnu |
2.30 | 9.4.0 | ✓ | 6.1.0 | ✓ |
mipsel-unknown-linux-musl |
1.1.24 | 9.2.0 | ✓ | 6.1.0 | ✓ |
powerpc-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
powerpc64-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
powerpc64le-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
riscv64gc-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
s390x-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
sparc64-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
sparcv9-sun-solaris |
1.22.7 | 8.4.0 | ✓ | N/A | |
thumbv6m-none-eabi [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv7em-none-eabi [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv7em-none-eabihf [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv7m-none-eabi [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv7neon-linux-androideabi [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
thumbv7neon-unknown-linux-gnueabihf |
2.31 | 9.4.0 | ✓ | N/A | ✓ |
thumbv8m.base-none-eabi [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv8m.main-none-eabi [4] |
3.3.0 | 9.2.1 | N/A | ||
thumbv8m.main-none-eabihf [4] |
3.3.0 | 9.2.1 | N/A | ||
wasm32-unknown-emscripten [6] |
3.1.14 | 15.0.0 | ✓ | N/A | ✓ |
x86_64-linux-android [1] |
9.0.8 | 9.0.8 | ✓ | 6.1.0 | ✓ |
x86_64-pc-windows-gnu |
N/A | 9.3 | ✓ | N/A | ✓ |
x86_64-sun-solaris |
1.22.7 | 8.4.0 | ✓ | N/A | |
x86_64-unknown-freebsd |
1.5 | 6.4.0 | ✓ | N/A | |
x86_64-unknown-dragonfly [2] [3] |
6.0.1 | 10.3.0 | ✓ | N/A | |
x86_64-unknown-illumos |
1.20.4 | 8.4.0 | ✓ | N/A | |
x86_64-unknown-linux-gnu |
2.31 | 9.4.0 | ✓ | 6.1.0 | ✓ |
x86_64-unknown-linux-gnu:centos [5] |
2.17 | 4.8.5 | ✓ | 4.2.1 | ✓ |
x86_64-unknown-linux-musl |
1.1.24 | 9.2.0 | ✓ | N/A | ✓ |
x86_64-unknown-netbsd [3] |
9.2.0 | 9.4.0 | ✓ | N/A |
[1] libc = bionic; Only works with native tests, that is, tests that do not depends on the
Android Runtime. For i686 some tests may fails with the error assertion failed: signal(libc::SIGPIPE, libc::SIG_IGN) != libc::SIG_ERR, see
issue #140 for more
information.
[2] No std component available.
[3] For some *BSD and Solaris targets, the libc column indicates the OS release version from which libc was extracted.
[4] libc = newlib
[5] Must change image = "ghcr.io/cross-rs/x86_64-unknown-linux-gnu:main-centos" in Cross.toml for [target.x86_64-unknown-linux-gnu] to use the CentOS7-compatible target.
[6] libc = emscripten and GCC = clang
[7] Must change image = "ghcr.io/cross-rs/aarch64-unknown-linux-gnu:main-centos" in Cross.toml for [target.aarch64-unknown-linux-gnu] to use the CentOS7-compatible target.
Additional Dockerfiles for other targets can be found in cross-toolchains. These include MSVC and Apple Darwin targets, which we cannot ship pre-built images of.
You can set the QEMU_STRACE variable when you use cross run to get a backtrace
of system calls from “foreign” (non x86_64) binaries.
$ cargo new --bin hello && cd $_
$ QEMU_STRACE=1 cross run --target aarch64-unknown-linux-gnu
9 brk(NULL) = 0x0000004000023000
9 uname(0x4000823128) = 0
(..)
9 write(1,0xa06320,14)Hello, world!
= 14
9 sigaltstack(0x4000823588,(nil)) = 0
9 munmap(0x0000004000b16000,16384) = 0
9 exit_group(0)
This crate is guaranteed to compile on stable Rust 1.64.0 and up. It might compile with older versions but that may change in any new patch release.
Some cross-compilation targets require a later Rust version, and using Xargo requires a nightly Rust toolchain.
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Contribution to this crate is organized under the terms of the Rust Code of Conduct, the maintainer of this crate, the cross-rs team, promises to intervene to uphold that code of conduct.