rust/cargo.sh

#!/bin/bash

if [ -z $CHANNEL ]; then
export CHANNEL='debug'
fi

pushd $(dirname "$0") >/dev/null
source config.sh

# read nightly compiler from rust-toolchain file
TOOLCHAIN=$(cat rust-toolchain)

popd >/dev/null

if [[ $(rustc -V) != $(rustc +${TOOLCHAIN} -V) ]]; then
    echo "rustc_codegen_cranelift is build for $(rustc +${TOOLCHAIN} -V) but the default rustc version is $(rustc -V)."
    echo "Using $(rustc +${TOOLCHAIN} -V)."
fi

cmd=$1
shift

cargo +${TOOLCHAIN} $cmd --target $TARGET_TRIPLE $@
Test rust-lang/regex example shootout-regex-dna 2019-07-30 13:37:47 +02:00			`#!/bin/bash`

			`if [ -z $CHANNEL ]; then`
			`export CHANNEL='debug'`
			`fi`

			`pushd $(dirname "$0") >/dev/null`
			`source config.sh`
Store nightly snapshot in rust-toolchain file, and use it in cargo.sh The rust-toolchain file can also store an exact nightly snapshot (instead of just "nightly"), so we can store whatever snapshot that rustc_codegen_cranelift is known to work with. This also lets us add a new feature to `cargo.sh` to let it use the exact same nightly snapshot as cg_clif. If there's a nightly compiler mismatch, you get a confusing error message like: error: couldn't load codegen backend "librustc_codegen_cranelift.so": "librustc_driver-681e2b4f66c73d3e.so: cannot open shared object file: No such file or directory" So doing this automatically in cargo.sh is useful. 2020-01-15 18:05:18 +01:00
			`# read nightly compiler from rust-toolchain file`
			`TOOLCHAIN=$(cat rust-toolchain)`

Test rust-lang/regex example shootout-regex-dna 2019-07-30 13:37:47 +02:00			`popd >/dev/null`

Display warning when overriding default rustc version in cargo.sh 2020-01-15 18:40:24 +01:00			`if [[ $(rustc -V) != $(rustc +${TOOLCHAIN} -V) ]]; then`
			`echo "rustc_codegen_cranelift is build for $(rustc +${TOOLCHAIN} -V) but the default rustc version is $(rustc -V)."`
			`echo "Using $(rustc +${TOOLCHAIN} -V)."`
			`fi`

Test rust-lang/regex example shootout-regex-dna 2019-07-30 13:37:47 +02:00			`cmd=$1`
			`shift`

Store nightly snapshot in rust-toolchain file, and use it in cargo.sh The rust-toolchain file can also store an exact nightly snapshot (instead of just "nightly"), so we can store whatever snapshot that rustc_codegen_cranelift is known to work with. This also lets us add a new feature to `cargo.sh` to let it use the exact same nightly snapshot as cg_clif. If there's a nightly compiler mismatch, you get a confusing error message like: error: couldn't load codegen backend "librustc_codegen_cranelift.so": "librustc_driver-681e2b4f66c73d3e.so: cannot open shared object file: No such file or directory" So doing this automatically in cargo.sh is useful. 2020-01-15 18:05:18 +01:00			`cargo +${TOOLCHAIN} $cmd --target $TARGET_TRIPLE $@`