rust/tests/run-make/metadata-flag-frobs-symbols/Makefile

# ignore-cross-compile
include ../tools.mk

all:
	$(RUSTC) foo.rs -C metadata=a -C extra-filename=-a
	$(RUSTC) foo.rs -C metadata=b -C extra-filename=-b
	$(RUSTC) bar.rs \
		--extern foo1=$(TMPDIR)/libfoo-a.rlib \
		--extern foo2=$(TMPDIR)/libfoo-b.rlib \
		--print link-args
	$(call RUN,bar)
ignore failing cross-compiled run-make tests `run-make-fulldeps` is never cross-compiled, so a lot of these tests never accounted for --target. Ignore them when cross-compiling for now. 2023-03-30 08:46:31 -05:00			`# ignore-cross-compile`
Diagnose missing includes in run-make tests 2022-08-23 00:00:00 +00:00			`include ../tools.mk`
rustc: Add a flag for specifying dependencies This comit implements a new flag, --extern, which is used to specify where a crate is located. The purpose of this flag is to bypass the normal crate loading/matching of the compiler to point it directly at the right file. This flag takes the form `--extern foo=bar` where `foo` is the name of a crate and `bar` is the location at which to find the crate. Multiple `--extern` directives are allowed with the same crate name to specify the rlib/dylib pair for a crate. It is invalid to specify more than one rlib or more than one dylib, and it's required that the crates are valid rust crates. I have also added some extensive documentation to metadata::loader about how crate loading should work. RFC: 0035-remove-crate-id 2014-07-01 08:37:54 -07:00
			`all:`
			`$(RUSTC) foo.rs -C metadata=a -C extra-filename=-a`
			`$(RUSTC) foo.rs -C metadata=b -C extra-filename=-b`
			`$(RUSTC) bar.rs \`
			`--extern foo1=$(TMPDIR)/libfoo-a.rlib \`
			`--extern foo2=$(TMPDIR)/libfoo-b.rlib \`
Stabilize -Z print-link-args as --print link-args We have stable options for adding linker arguments; we should have a stable option to help debug linker arguments. 2021-12-06 14:09:24 -08:00			`--print link-args`
rustc: Add a flag for specifying dependencies This comit implements a new flag, --extern, which is used to specify where a crate is located. The purpose of this flag is to bypass the normal crate loading/matching of the compiler to point it directly at the right file. This flag takes the form `--extern foo=bar` where `foo` is the name of a crate and `bar` is the location at which to find the crate. Multiple `--extern` directives are allowed with the same crate name to specify the rlib/dylib pair for a crate. It is invalid to specify more than one rlib or more than one dylib, and it's required that the crates are valid rust crates. I have also added some extensive documentation to metadata::loader about how crate loading should work. RFC: 0035-remove-crate-id 2014-07-01 08:37:54 -07:00			`$(call RUN,bar)`