From b97fd6c2665ea5c51522b2a94abc22fc34e83f49 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E8=AE=B8=E6=9D=B0=E5=8F=8B=20Jieyou=20Xu=20=28Joe=29?= <39484203+jieyouxu@users.noreply.github.com> Date: Mon, 24 Jun 2024 13:21:15 +0800 Subject: [PATCH] tests: document how to run `run-make` on Windows (#2002) --- src/tests/running.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/src/tests/running.md b/src/tests/running.md index a4f77aa3..ca0ceb75 100644 --- a/src/tests/running.md +++ b/src/tests/running.md @@ -213,6 +213,22 @@ This is much faster, but doesn't always work. For example, some tests include directives that specify specific compiler flags, or which rely on other crates, and they may not run the same without those options. +## Running `run-make` tests + +### Windows + +Running the `run-make` test suite on Windows is a bit more involved. There are numerous +prerequisites and environmental requirements: + +- Install msys2: +- Specify `MSYS2_PATH_TYPE=inherit` in `msys2.ini` in the msys2 installation directory, run the + following with `MSYS2 MSYS`: + - `pacman -Syuu` + - `pacman -S make` + - `pacman -S diffutils` + - `pacman -S binutils` + - `./x test run-make` (`./x test tests/run-make` doesn't work) + ## Running tests on a remote machine