build/cargo-linker
author Ryan VanderMeulen <ryanvm@gmail.com>
Thu, 21 Sep 2017 09:49:52 -0400
changeset 431725 a2e26860d2a9c67beda535586b6eef81a575624e
parent 403820 fc34b2a31c4beb821ab40c8eca744c78212c14f5
child 444518 69465fa861e14da6b903ec4f154abf355e5d6d79
permissions -rwxr-xr-x
Bug 1398514 - Skip browser_ext_tabs_executeScript_runAt.js for frequent failures. a=test-only

#!/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.

${MOZ_CARGO_WRAP_LD} ${MOZ_CARGO_WRAP_LDFLAGS} "$@"