diff options
| author | Rolf Eike Beer <eb@emlix.com> | 2024-12-17 14:41:17 +0100 |
|---|---|---|
| committer | Dylan Baker <dylan@pnwbakers.com> | 2024-12-20 09:24:24 -0800 |
| commit | e9e582020898e52d17b4c48afe65589bc1dee065 (patch) | |
| tree | 62d31b717c4c7827abc79e476a2016978efa005a /unittests/linuxcrosstests.py | |
| parent | 79fc8941c5d3855ebd76aad90550081e455cc50f (diff) | |
| download | meson-e9e582020898e52d17b4c48afe65589bc1dee065.tar.gz | |
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.
Diffstat (limited to 'unittests/linuxcrosstests.py')
| -rw-r--r-- | unittests/linuxcrosstests.py | 2 |
1 files changed, 1 insertions, 1 deletions
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 |