From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] meson: Only generate trace files for selected targets
Date: Wed, 24 Feb 2021 13:26:24 +0100 [thread overview]
Message-ID: <39cc99dd-54d5-9dd1-d66a-7947686dbada@redhat.com> (raw)
In-Reply-To: <20210224120923.3154325-1-philmd@redhat.com>
On 24/02/21 13:09, Philippe Mathieu-Daudé wrote:
> We don't need to generate trace files for targets we
> are not building. Restrict the the ones selected.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> meson.build | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index 05a67c20d93..c9b0433667d 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1826,15 +1826,6 @@
> trace_events_subdirs += [
> 'accel/tcg',
> 'hw/core',
> - 'target/arm',
> - 'target/hppa',
> - 'target/i386',
> - 'target/i386/kvm',
> - 'target/mips',
> - 'target/ppc',
> - 'target/riscv',
> - 'target/s390x',
> - 'target/sparc',
> ]
> endif
>
> @@ -2166,6 +2157,7 @@
> t = target_arch[arch].apply(config_target, strict: false)
> arch_srcs += t.sources()
> arch_deps += t.dependencies()
> + trace_events_subdirs += ['target' / arch]
>
> target_common = common_ss.apply(config_target, strict: false)
> objects = common_all.extract_objects(target_common.sources())
>
Is this still okay if there is no trace-events file for a given arch?
Paolo
next prev parent reply other threads:[~2021-02-24 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 12:09 [PATCH] meson: Only generate trace files for selected targets Philippe Mathieu-Daudé
2021-02-24 12:26 ` Paolo Bonzini [this message]
2021-02-24 12:51 ` Philippe Mathieu-Daudé
2021-02-24 18:02 ` Philippe Mathieu-Daudé
2021-02-24 13:11 ` Peter Maydell
2021-02-24 13:30 ` Philippe Mathieu-Daudé
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=39cc99dd-54d5-9dd1-d66a-7947686dbada@redhat.com \
--to=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).