From e9e582020898e52d17b4c48afe65589bc1dee065 Mon Sep 17 00:00:00 2001 From: Rolf Eike Beer Date: Tue, 17 Dec 2024 14:41:17 +0100 Subject: print out which command needs an exe_wrapper It's not the first time I run into an issue with an intentionally missing exe_wrapper during cross compilation. In pretty much all the cases the project I tried to build already had code available to not need one in the first place. Print out what command was actually the culprit to make debugging this easier. --- unittests/linuxcrosstests.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'unittests/linuxcrosstests.py') diff --git a/unittests/linuxcrosstests.py b/unittests/linuxcrosstests.py index a35633cdd..910429b0e 100644 --- a/unittests/linuxcrosstests.py +++ b/unittests/linuxcrosstests.py @@ -146,7 +146,7 @@ class LinuxCrossMingwTests(BaseLinuxCrossTests): self.meson_cross_files = [os.path.join(testdir, 'broken-cross.txt')] # Force tracebacks so we can detect them properly env = {'MESON_FORCE_BACKTRACE': '1'} - error_message = "An exe_wrapper is needed but was not found. Please define one in cross file and check the command and/or add it to PATH." + error_message = "An exe_wrapper is needed for " + self.builddir + "/prog.exe but was not found. Please define one in cross file and check the command and/or add it to PATH." with self.assertRaises(MesonException) as cm: # Must run in-process or we'll get a generic CalledProcessError -- cgit v1.2.3