gecko-dev/taskcluster/scripts/misc/osx-cross-linker

exec $MOZ_FETCHES_DIR/clang/bin/clang -v \
  -fuse-ld=$MOZ_FETCHES_DIR/cctools/bin/x86_64-apple-darwin-ld \
  -mmacosx-version-min=10.11 \
  -target $TARGET \
  -B $MOZ_FETCHES_DIR/cctools/bin \
  -isysroot $MOZ_FETCHES_DIR/MacOSX10.11.sdk \
  "$@"
Bug 1534533 - Add geckodriver toolchain tasks. r=chmanchester There was quite a bit of discussion of this in `#build` on IRC, and the consensus was that geckodriver should be built as a stand-alone Rust crate and not as part of Firefox/Gecko (say, as a new --enable-project target). This follows that approach, and the expression, modeled off of cbindgen but updated to cross compile from a Linux host to all targets, is pretty straight-forward. A sparse profile would be nice, but the way that the Gecko Cargo workspace works means that the profile must accumulate Rust code from many locations. If we want to, eventually testing/geckodriver can be removed from the top-level Rust workspace, the geckodriver-signing tasks migrated to these toolchain tasks, consumers migrated to the signing tasks, and geckodriver removed from the "common" test archive. Differential Revision: https://phabricator.services.mozilla.com/D43646 --HG-- rename : taskcluster/scripts/misc/vs-setup.sh => taskcluster/scripts/misc/vs-setup32.sh extra : moz-landing-system : lando 2019-08-28 23:54:06 +03:00			`exec $MOZ_FETCHES_DIR/clang/bin/clang -v \`
			`-fuse-ld=$MOZ_FETCHES_DIR/cctools/bin/x86_64-apple-darwin-ld \`
			`-mmacosx-version-min=10.11 \`
			`-target $TARGET \`
			`-B $MOZ_FETCHES_DIR/cctools/bin \`
			`-isysroot $MOZ_FETCHES_DIR/MacOSX10.11.sdk \`
			`"$@"`