From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path
Date: Thu, 7 Jul 2022 09:47:52 -0400 [thread overview]
Message-ID: <20220707094752.6ec14f7a@gandalf.local.home> (raw)
In-Reply-To: <20220707121542.28434-1-dwagner@suse.de>
On Thu, 7 Jul 2022 14:15:41 +0200
Daniel Wagner <dwagner@suse.de> wrote:
> The libtraceevent pkg-config generated by meson is not adding the
> subdirectory to the CLFAGS. This is generally a good idea in order to
> avoid any file name collisions. Hence use explicit include paths for
> libtraceevent.
Is there a way to fix this. Honestly, I hate the libtraceevent name (should
at least be traceevent), and I have been thinking of changing it.
If we do not have pkg-config working and everything needs to add explicit
include paths, then I'll never be able to change it, or even just get rid
of the subdirectory.
-- Steve
next prev parent reply other threads:[~2022-07-07 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 12:15 [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path Daniel Wagner
2022-07-07 12:15 ` [RFC v1 2/2] libtracefs: Add initial support for meson Daniel Wagner
2022-07-07 13:47 ` Steven Rostedt [this message]
2022-07-07 14:07 ` [RFC v1 1/2] libtracefs: Use explicit libtraceevent include path Daniel Wagner
2022-07-07 14:26 ` Steven Rostedt
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=20220707094752.6ec14f7a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dwagner@suse.de \
--cc=linux-trace-users@vger.kernel.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 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).