From: Jim MacArthur <jim.macarthur@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v3 1/2] meson: Restrict gdbstub to user/system builds
Date: Fri, 27 Feb 2026 11:45:32 +0000 [thread overview]
Message-ID: <aaGD3FRwRW-H3Ex-@linaro.org> (raw)
In-Reply-To: <20260227101040.70763-2-philmd@linaro.org>
On Fri, Feb 27, 2026 at 11:10:38AM +0100, Philippe Mathieu-Daudé wrote:
> Limited builds (tools, documentation) don't need to generate /
> build gdbstub files. Only process the gdbstub/ folder when
> user / system emulation / acceleration is built.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 3cd1d8dbc66..60415df69a1 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -3724,7 +3724,6 @@ subdir('qom')
> subdir('authz')
> subdir('crypto')
> subdir('ui')
> -subdir('gdbstub')
> if have_system
> subdir('hw')
> else
> @@ -3767,6 +3766,7 @@ if have_system or have_user
> output: 'decode-@BASENAME@.c.inc',
> arguments: ['@INPUT@', '@EXTRA_ARGS@', '-o', '@OUTPUT@'])
> subdir('libdecnumber')
> + subdir('gdbstub')
> subdir('target')
> endif
>
> --
> 2.52.0
>
>
Reviewed-by: Jim MacArthur <jim.macarthur@linaro.org>
next prev parent reply other threads:[~2026-02-27 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:10 [PATCH v3 0/2] gdbstub: Generate a single gdbstub-xml.c / gdb_static_features[] Philippe Mathieu-Daudé
2026-02-27 10:10 ` [PATCH v3 1/2] meson: Restrict gdbstub to user/system builds Philippe Mathieu-Daudé
2026-02-27 11:45 ` Jim MacArthur [this message]
2026-02-27 10:10 ` [PATCH v3 2/2] gdbstub: Generate a single gdbstub-xml.c / gdb_static_features[] Philippe Mathieu-Daudé
2026-02-27 11:46 ` Jim MacArthur
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=aaGD3FRwRW-H3Ex-@linaro.org \
--to=jim.macarthur@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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.