ripgrep/Cross.toml

[target.x86_64-unknown-linux-musl]
image = "burntsushi/cross:x86_64-unknown-linux-musl"

[target.i686-unknown-linux-gnu]
image = "burntsushi/cross:i686-unknown-linux-gnu"

[target.mips64-unknown-linux-gnuabi64]
image = "burntsushi/cross:mips64-unknown-linux-gnuabi64"
build-std = true

[target.arm-unknown-linux-gnueabihf]
image = "burntsushi/cross:arm-unknown-linux-gnueabihf"
ci: fix musl deployment The docker image that the Linux binary is now built in does not have ASCII doc installed, so setup Cross to point to my own image with those tools installed. 2019-08-01 18:41:44 -04:00			`[target.x86_64-unknown-linux-musl]`
ci: fix musl docker build Looks like the old japaric images are bunk. We update our docker image to be based on the new rustembedded images and configure cross to use it. Turns out that this wasn't due to a stale docker image, but rather, a bug in cross: https://github.com/rust-embedded/cross/issues/357 We work around that bug by installing the master branch of cross. Sigh. 2020-01-09 21:54:28 -05:00			`image = "burntsushi/cross:x86_64-unknown-linux-musl"`
ci: switch build to GitHub Actions 2020-02-18 18:15:30 -05:00
			`[target.i686-unknown-linux-gnu]`
			`image = "burntsushi/cross:i686-unknown-linux-gnu"`

			`[target.mips64-unknown-linux-gnuabi64]`
			`image = "burntsushi/cross:mips64-unknown-linux-gnuabi64"`
ci: try to fix CI 2023-07-05 11:39:15 -04:00			`build-std = true`
ci: switch build to GitHub Actions 2020-02-18 18:15:30 -05:00
			`[target.arm-unknown-linux-gnueabihf]`
			`image = "burntsushi/cross:arm-unknown-linux-gnueabihf"`