rust/tests/run-make/rlib-chain/Makefile

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

all:
	$(RUSTC) m1.rs
	$(RUSTC) m2.rs
	$(RUSTC) m3.rs
	$(RUSTC) m4.rs
	$(call RUN,m4)
	rm $(TMPDIR)/*lib
	$(call RUN,m4)
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-22 19:00:00 -05:00			`include ../tools.mk`
Add a new run-make test directory This infrastructure is meant to support runnings tests that involve various interesting interdependencies about the types of crates being linked or possibly interacting with C libraries. The goal of these make tests is to not restrict them to a particular test runner, but allow each test to run its own tests. To this end, there is a new src/test/run-make directory which has sub-folders of tests. Each test requires a `Makefile`, and running the tests constitues simply running `make` inside the directory. The new target is `check-stageN-rmake`. These tests will have the destination directory (as TMPDIR) and the local rust compiler (as RUSTC) passed along to them. There is also some helpful cross-platform utilities included in src/test/run-make/tools.mk to aid with compiling C programs and running them. The impetus for adding this new test suite is to allow various interesting forms of testing rust linkage. All of the tests initially added are various flavors of compiling Rust and C with one another as well as just making sure that rust linkage works in general. Closes #10434 2013-11-16 19:07:32 -06:00
			`all:`
			`$(RUSTC) m1.rs`
			`$(RUSTC) m2.rs`
			`$(RUSTC) m3.rs`
			`$(RUSTC) m4.rs`
			`$(call RUN,m4)`
			`rm $(TMPDIR)/*lib`
			`$(call RUN,m4)`