From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Patrick McLean <patrick.mclean@sony.com>,
John Kacur <jkacur@redhat.com>,
Alan Mikhak <amikhak@wirelessfabric.com>,
Seth Forshee <seth.forshee@canonical.com>,
Tony Jones <tonyj@suse.de>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Nivedita Swaminathan <nivedita.swaminathan@intel.com>
Subject: Re: Getting libtraceevent into a packaged library
Date: Fri, 4 Oct 2019 11:51:12 +0900 [thread overview]
Message-ID: <CAM9d7ciT2NtY9_m_scxom-POvKJR_LV-JaCxC+B78dc=DezuzQ@mail.gmail.com> (raw)
In-Reply-To: <20191003150104.74216a0a@gandalf.local.home>
Hi Steve,
On Fri, Oct 4, 2019 at 4:01 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> What's the next step to get this into a package so that perf,
> trace-cmd, power-top, rasdaemon, uftrace, and whatever does not need to
> have its own copy of the code, but instead link to it.
>
> Note, the interface has changed since other tools copied it, and I'm
> willing to help anyone out in porting to the package.
For uftrace, I think it needs to keep the copy of the code for a while
since it should support older versions of distros as well.
I'll add a runtime dependency check for libtraceevent and use
the new APIs if exists.
Thanks,
Namhyung
next prev parent reply other threads:[~2019-10-04 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 19:01 Getting libtraceevent into a packaged library Steven Rostedt
2019-10-03 19:22 ` Tony Jones
2019-10-04 2:51 ` Namhyung Kim [this message]
2019-10-04 13:33 ` Steven Rostedt
2019-10-06 14:15 ` Namhyung Kim
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='CAM9d7ciT2NtY9_m_scxom-POvKJR_LV-JaCxC+B78dc=DezuzQ@mail.gmail.com' \
--to=namhyung@kernel.org \
--cc=amikhak@wirelessfabric.com \
--cc=jkacur@redhat.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nivedita.swaminathan@intel.com \
--cc=patrick.mclean@sony.com \
--cc=rostedt@goodmis.org \
--cc=seth.forshee@canonical.com \
--cc=tonyj@suse.de \
/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).