gecko-dev/build/cargo-host-linker

#!/bin/sh
# See comment in cargo-linker.
eval ${MOZ_CARGO_WRAP_HOST_LD} '"$@"' ${MOZ_CARGO_WRAP_HOST_LDFLAGS}
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 11:05:18 +00:00			`#!/bin/sh`
			`# See comment in cargo-linker.`
Bug 1916426 - Pass our LDFLAGS last to the linker command line cargo invokes r=firefox-build-system-reviewers,sergesanspaille See https://github.com/llvm/llvm-project/issues/107365#issuecomment-2362516002 for an example of how things can go wrong when they are passed first. I don't think there was a specific reason for them to have been put first in the first place. Differential Revision: https://phabricator.services.mozilla.com/D222899 2024-09-20 06:56:25 +00:00			`eval ${MOZ_CARGO_WRAP_HOST_LD} '"$@"' ${MOZ_CARGO_WRAP_HOST_LDFLAGS}`