linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: 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>,
	Namhyung Kim <namhyung@kernel.org>,
	Nivedita Swaminathan <nivedita.swaminathan@intel.com>
Subject: Getting libtraceevent into a packaged library
Date: Thu, 3 Oct 2019 15:01:04 -0400	[thread overview]
Message-ID: <20191003150104.74216a0a@gandalf.local.home> (raw)

Hello folks,

I've Cc'd everyone that might be interested in helping package
libtraceveent. It is basically ready to become a full library package.
I only have a couple of patches to deal with SPDX headers and such, but
other than that, I think we are good to go.

My question is now, how to we go about having distributions package it.
Like perf, the main source code lives in the Linux kernel source tree
under:

 tools/lib/traceevent

I'd like to install the following headers in /usr/include

  event-parse.h
  kbuffer.h
  trace-seq.h

And the following libraries:

  libtraceevent.so (with all its versions)

Documentation man pages are in the Documentation directory.

And we should have plugins installed as well.

If we had done everything correctly, a "make install" in that directory
will move all the files to their proper location.

make doc will create the man pages.

make doc-install will install the man pages.

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.

Let me know of anyone else that can help in getting this packaged for a
Linux distribution.

-- Steve

             reply	other threads:[~2019-10-03 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 19:01 Steven Rostedt [this message]
2019-10-03 19:22 ` Getting libtraceevent into a packaged library Tony Jones
2019-10-04  2:51 ` Namhyung Kim
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=20191003150104.74216a0a@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=amikhak@wirelessfabric.com \
    --cc=jkacur@redhat.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=nivedita.swaminathan@intel.com \
    --cc=patrick.mclean@sony.com \
    --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).