@@ -11,15 +11,65 @@
# Contributors:
# Peter Maydell (Linaro) - initial implementation
-# So we notice risugen failing even though it's in a pipeline
-set -o pipefail
+# Simple usage
+usage() {
+ cat <<-EOF
+ Usage: $0 [options]
+
+ Options include:
+ --use-docker[=tags] use docker cross compile
+
+ If specifying docker the default will be to use the any
+ qemu:debian-FOO-cross targets available on your system.
+EOF
+ exit 1
+}
+
+while [[ "$1" = -* ]]; do
+ opt="$1"; shift
+ arg=
+ if [[ "$opt" = *=* ]]; then
+ arg="${opt#*=}"
+ opt="${opt%%=*}"
+ fi
+ case "$opt" in
+ --use-docker)
+ if [ -z "$arg" ]; then
+ default_tags=$(docker images qemu --format "{{.Repository}}:{{.Tag}}" | grep "\(arm\|power\).*cross$")
+ docker_tags=$(echo $default_tags | sed 's/\n/\s/g' )
+ else
+ docker_tags="$arg"
+ fi
+ ;;
+ --help)
+ usage
+ ;;
+ *)
+ usage
+ ;;
+ esac
+done
# Debian stretch and Ubuntu Xenial have cross compiler packages for
# all of these:
-# gcc-arm-linux-gnueabihf gcc-aarch64-linux-gnu gcc-m68k-linux-gnu
-# gcc-powerpc64le-linux-gnu gcc-powerpc64-linux-gnu
+# gcc-arm-linux-gnueabihf gcc-aarch64-linux-gnu gcc-m68k-linux-gnu
+# gcc-powerpc64le-linux-gnu gcc-powerpc64-linux-gnu
+# If docker is enabled we just brute force the various images until we
+# can set the one that has a workable cross compiler.
+
+DOCKER_RUN="docker run --rm -t -u $(id -u) -v $(pwd):$(pwd) -w $(pwd)"
program_exists() {
+ if [ ! -z "$docker_tags" ]; then
+ use_docker_tag=""
+ for tag in $docker_tags; do
+ if ${DOCKER_RUN} ${tag} /bin/bash -c "command -v $1 >/dev/null"; then
+ use_docker_tag=$tag
+ return
+ fi
+ done
+ fi
+
command -v "$1" >/dev/null 2>&1
}
@@ -30,19 +80,29 @@ for triplet in aarch64-linux-gnu arm-linux-gnueabihf m68k-linux-gnu \
if ! program_exists "${triplet}-gcc"; then
echo "Skipping ${triplet}: no compiler found"
continue
+ else
+ echo "Building ${triplet} on ${use_docker_tag:-host}..."
fi
# Do a complete rebuild from scratch, because it's cheap enough.
rm -rf build/${triplet}
mkdir -p build/${triplet}
- (cd build/${triplet} && CROSS_PREFIX="${triplet}-" ../../configure)
- make -C build/${triplet} EXTRA_CFLAGS=-Werror
+ CONFIGURE="cd build/${triplet} && CROSS_PREFIX="${triplet}-" ../../configure"
+ MAKE="make -C build/${triplet} EXTRA_CFLAGS=-Werror"
+ if [ -z "$use_docker_tag" ]; then
+ /bin/bash -c "${CONFIGURE}"
+ ${MAKE}
+ else
+ ${DOCKER_RUN} $use_docker_tag /bin/bash -c "${CONFIGURE}"
+ ${DOCKER_RUN} $use_docker_tag /bin/bash -c "${MAKE}"
+ fi
done
# Now run risugen for all architectures
mkdir -p build/risuout
+set -o pipefail # detect failures in pipeline
for f in *.risu; do
echo "Running risugen on $f..."
If we want to link to any other libraries we might find using simple cross toolchains doesn't work so well. One way around this is to use a dockerised cross-toolchain which then won't clash with your host system. If the user specifies --use-docker the obvious will be done. By default we use the QEMU projects qemu:debian-FOO-cross images as RISU hackers are likely to be QEMU developers too. However any docker tag can be passed on the command line. If none of the docker images have usable compilers we fall back to checking the host path. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> --- build-all-archs | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 66 insertions(+), 6 deletions(-) -- 2.13.0