gecko-dev/build/cargo-linker

#!/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 each 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} '"$@"'
Bug 1329737 - part 3 - use an alternate linker for Cargo invocations; r=rillian For linking static libraries, rustc will use whatever `cc` it finds (or the equivalent on Windows). For our purposes, however, `cc` is not what we use to link and we may have additional options we would like to pass to the linker. To do this, we need to tell Cargo about our alternate linker (currently only used for target compilations, on the theory that the host compiler rustc finds is probably good enough) and we also need to pass our linker options into the process. We do this with environment variables, which is not a great solution, but works surprisingly well. This alternate linker is disabled for ASan builds due to peculiar crashes when running Rust build scripts and for Windows, because we don't do any interesting cross-compiling there. 2017-04-28 21:06:41 +03:00			`#!/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,`
Bug 1524396 - Unify how target/host linker/flags are passed to rust. r=chmanchester The current setup uses different ways for different platforms, with different workarounds, even using extra configuration items for Windows. Now that there can't be a difference between the host per the build system and the host per rust, we can get rid of those configuration items, and use a more common infrastructure. We cannot, however, avoid using wrapper scripts, because per-target rust link-arg flags don't work up great. The downside is that multiplies the number of wrappers, as we now have to have a different one for host and target, and then we have .bat files and shell scripts for, respectively, Windows hosts, and other hosts. Depends on D24321 Differential Revision: https://phabricator.services.mozilla.com/D24322 --HG-- extra : moz-landing-system : lando 2019-03-22 14:05:18 +03:00			`# and not quoting it ensures that each of those arguments is passed`
Bug 1329737 - part 3 - use an alternate linker for Cargo invocations; r=rillian For linking static libraries, rustc will use whatever `cc` it finds (or the equivalent on Windows). For our purposes, however, `cc` is not what we use to link and we may have additional options we would like to pass to the linker. To do this, we need to tell Cargo about our alternate linker (currently only used for target compilations, on the theory that the host compiler rustc finds is probably good enough) and we also need to pass our linker options into the process. We do this with environment variables, which is not a great solution, but works surprisingly well. This alternate linker is disabled for ASan builds due to peculiar crashes when running Rust build scripts and for Windows, because we don't do any interesting cross-compiling there. 2017-04-28 21:06:41 +03:00			`# as a separate argument to the actual LD.`
Bug 1418598 - Make cargo-linker properly handle quoted strings in MOZ_CARGO_WRAP_LD and MOZ_CARGO_WRAP_LDFLAGS. r=ted --HG-- extra : rebase_source : 84bcb0718584adf7a082b657cd8ff7cc8579e346 2017-11-18 14:24:12 +03:00			`#`
			`# $@ is doubly quoted for the eval. See bug 1418598.`
Bug 1329737 - part 3 - use an alternate linker for Cargo invocations; r=rillian For linking static libraries, rustc will use whatever `cc` it finds (or the equivalent on Windows). For our purposes, however, `cc` is not what we use to link and we may have additional options we would like to pass to the linker. To do this, we need to tell Cargo about our alternate linker (currently only used for target compilations, on the theory that the host compiler rustc finds is probably good enough) and we also need to pass our linker options into the process. We do this with environment variables, which is not a great solution, but works surprisingly well. This alternate linker is disabled for ASan builds due to peculiar crashes when running Rust build scripts and for Windows, because we don't do any interesting cross-compiling there. 2017-04-28 21:06:41 +03:00
Bug 1418598 - Make cargo-linker properly handle quoted strings in MOZ_CARGO_WRAP_LD and MOZ_CARGO_WRAP_LDFLAGS. r=ted --HG-- extra : rebase_source : 84bcb0718584adf7a082b657cd8ff7cc8579e346 2017-11-18 14:24:12 +03:00			`eval ${MOZ_CARGO_WRAP_LD} ${MOZ_CARGO_WRAP_LDFLAGS} '"$@"'`