build/cargo-linker
author Blake Kaplan <mrbkap@gmail.com>
Thu, 22 Feb 2018 16:30:37 -0800
changeset 464094 544d195743e3ba3022fe025a305af977eec7b4d3
parent 447035 69465fa861e14da6b903ec4f154abf355e5d6d79
child 527416 3a444460cb6c3db935838ce735f1e6edceb55dfa
permissions -rwxr-xr-x
Bug 1326028 - We now upgrade elements in the proper order. r=smaug MozReview-Commit-ID: Dt4sc8FYmT7

#!/bin/sh

# If you want to use a custom linker with Cargo, Cargo requires that you
# specify it in Cargo.toml or via the matching environment variable.
# Passing extra options to the linker is possible with Cargo via
# RUSTFLAGS='-C link-args', but testing showed that doing this reliably
# was difficult.
#
# Our solution to these problems is to use this wrapper script.  We pass
# in the LD and the LDFLAGS to use via environment variables.  Note that
# we do *not* quote either MOZ_CARGO_WRAP variable:
#
# * MOZ_CARGO_WRAP_LD is equivalent to CC on Unix-y platforms, and CC
#   frequently has additional arguments in addition to the compiler
#   itself.
# * MOZ_CARGO_WRAP_LDFLAGS contains space-separated arguments to pass,
#   and not quoting it ensures that either of those arguments is passed
#   as a separate argument to the actual LD.
#
# $@ is doubly quoted for the eval. See bug 1418598.

eval ${MOZ_CARGO_WRAP_LD} ${MOZ_CARGO_WRAP_LDFLAGS} '"$@"'