From: Joshua Watt <jpewhacker@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Cc: Rong Fu <rong.fu.cn@windriver.com>, Joshua Watt <JPEWhacker@gmail.com>
Subject: [yocto][meta-mingw][wrynose][PATCH] mingw32-common.inc: disable meson exe wrapper for mingw targets
Date: Mon, 20 Jul 2026 10:02:25 -0600 [thread overview]
Message-ID: <20260720160225.535024-1-JPEWhacker@gmail.com> (raw)
From: Rong Fu <rong.fu.cn@windriver.com>
The meson bbclass uses qemu as an exe_wrapper to run cross-compiled
binaries for sanity checks. However, qemu-i386 cannot execute Windows
PE format executables (.exe), causing meson setup to fail with:
Executables created by c compiler i686-w64-mingw32-gcc are not runnable.
This affects all meson-based nativesdk recipes when SDKMACHINE is set
to a mingw target (e.g. i686-mingw32), such as nativesdk-dtc.
Disable EXEWRAPPER_ENABLED for mingw32 to skip the qemu exe wrapper
since it is not functional for Windows targets.
Signed-off-by: Rong Fu <rong.fu.cn@windriver.com>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
conf/machine-sdk/include/mingw32-common.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc
index bf3f14e..6014c51 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -57,6 +57,9 @@ DISABLE_STATIC:mingw32 = ""
# disable security flags
GCCPIE:mingw32 = ""
+# qemu cannot run Windows PE executables, disable meson exe wrapper
+EXEWRAPPER_ENABLED:mingw32 = "False"
+
# wine and wineserver are required to test MinGW SDKs
HOSTTOOLS_NONFATAL += "wine wineserver"
--
2.54.0
reply other threads:[~2026-07-20 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260720160225.535024-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=rong.fu.cn@windriver.com \
--cc=yocto-patches@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.