From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH v2 1/4] meson: add trace_events_config[]
Date: Tue, 24 Nov 2020 17:02:52 +0100 [thread overview]
Message-ID: <20201124160255.28111-2-kraxel@redhat.com> (raw)
In-Reply-To: <20201124160255.28111-1-kraxel@redhat.com>
It's an array of dicts, where each dict holds the configuration for one
trace-events file. For now just fill it from trace_events_subdirs.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
meson.build | 1 +
trace/meson.build | 21 ++++++++++++++++-----
2 files changed, 17 insertions(+), 5 deletions(-)
diff --git a/meson.build b/meson.build
index 5062407c7052..b62f71c6b4f1 100644
--- a/meson.build
+++ b/meson.build
@@ -1386,6 +1386,7 @@ target_softmmu_arch = {}
# TODO: add each directory to the subdirs from its own meson.build, once
# we have those
+trace_events_config = []
trace_events_subdirs = [
'accel/kvm',
'accel/tcg',
diff --git a/trace/meson.build b/trace/meson.build
index 843ea1449540..552371b84241 100644
--- a/trace/meson.build
+++ b/trace/meson.build
@@ -1,12 +1,23 @@
specific_ss.add(files('control-target.c'))
trace_events_files = []
-foreach dir : [ '.' ] + trace_events_subdirs
- trace_events_file = meson.source_root() / dir / 'trace-events'
+
+trace_events_config += {
+ 'file' : meson.source_root() / 'trace-events',
+ 'group' : 'root',
+}
+foreach dir : trace_events_subdirs
+ trace_events_config += {
+ 'file' : meson.source_root() / dir / 'trace-events',
+ 'group' : dir.underscorify(),
+ }
+endforeach
+
+foreach c : trace_events_config
+ trace_events_file = c.get('file')
trace_events_files += [ trace_events_file ]
- group_name = dir == '.' ? 'root' : dir.underscorify()
- group = '--group=' + group_name
- fmt = '@0@-' + group_name + '.@1@'
+ group = '--group=' + c.get('group')
+ fmt = '@0@-' + c.get('group') + '.@1@'
trace_h = custom_target(fmt.format('trace', 'h'),
output: fmt.format('trace', 'h'),
--
2.27.0
next prev parent reply other threads:[~2020-11-24 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 16:02 [PATCH v2 0/4] [RfC] fix tracing for modules Gerd Hoffmann
2020-11-24 16:02 ` Gerd Hoffmann [this message]
2020-11-24 16:02 ` [PATCH v2 2/4] meson: move up hw subdir (specifically before trace subdir) Gerd Hoffmann
2020-11-24 16:02 ` [PATCH v2 3/4] meson: add module_trace & module_trace_src Gerd Hoffmann
2020-11-24 16:02 ` [PATCH v2 4/4] meson: move qxl trace events to separate file Gerd Hoffmann
2020-11-30 16:56 ` [PATCH v2 0/4] [RfC] fix tracing for modules Stefan Hajnoczi
2020-12-03 10:39 ` Gerd Hoffmann
2020-12-15 16:36 ` Gerd Hoffmann
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=20201124160255.28111-2-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@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).