From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 00/13] trace-cmd: Clean ups to the Makefile for using external libraries
Date: Fri, 11 Dec 2020 12:08:42 -0500 [thread overview]
Message-ID: <20201211170842.611554918@goodmis.org> (raw)
Now that libtraceevent and libtracefs are in their separate repositories,
clean up the Makefiles for trace-cmd a bit, and even let the builder know
that libtraceevent and libtracefs are separate and where to find them.
Steven Rostedt (VMware) (13):
trace-cmd: Add missing SPDX headers
trace-cmd: Allow overriding of pkg-config
trace-cmd: Use $(LIBTRACECMD_STATIC) instead of open coding in Makefile
trace-cmd: Add versioning to libtracecmd.so
trace-cmd: Add pkg-config configuration for libtracecmd.so
trace-cmd: Clean up the Makefiles a little
trace-cmd: Remove making of ld.so.conf.d/trace.conf
trace-cmd: Install libtracecmd in the proper lib directory
trace-cmd: Move the installing of libtracecmd to the lib/trace-cmd Makefile
trace-cmd: Install the soft links for libtracecmd.so
trace-cmd: Do not install libtracefs nor libtraceevent libraries
trace-cmd: Do not build shared libraries for libtracefs and libtraceevent
trace-cmd: Add warning if libtracefs or libtraceevent are not found
----
Makefile | 119 +++++++++++++++-----------
features.mk | 1 +
include/linux/time64.h | 2 +
lib/trace-cmd/Makefile | 27 ++++--
lib/trace-cmd/include/private/trace-msg.h | 1 +
lib/traceevent/Makefile | 19 +++-
lib/traceevent/plugins/Makefile | 2 +
lib/traceevent/plugins/plugin_python_loader.c | 1 +
lib/tracefs/Makefile | 20 +++--
libtracecmd.pc.template | 10 +++
python/Makefile | 2 +
scripts/utils.mk | 13 ++-
tracecmd/Makefile | 1 +
tracecmd/include/bug.h | 1 +
tracecmd/trace-usage.c | 1 +
utest/Makefile | 1 +
16 files changed, 148 insertions(+), 73 deletions(-)
create mode 100644 libtracecmd.pc.template
next reply other threads:[~2020-12-11 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 17:08 Steven Rostedt [this message]
2020-12-11 17:08 ` [PATCH 01/13] trace-cmd: Add missing SPDX headers Steven Rostedt
2020-12-11 17:08 ` [PATCH 02/13] trace-cmd: Allow overriding of pkg-config Steven Rostedt
2020-12-11 17:08 ` [PATCH 03/13] trace-cmd: Use $(LIBTRACECMD_STATIC) instead of open coding in Makefile Steven Rostedt
2020-12-11 17:08 ` [PATCH 04/13] trace-cmd: Add versioning to libtracecmd.so Steven Rostedt
2020-12-11 17:08 ` [PATCH 05/13] trace-cmd: Add pkg-config configuration for libtracecmd.so Steven Rostedt
2020-12-11 17:08 ` [PATCH 06/13] trace-cmd: Clean up the Makefiles a little Steven Rostedt
2020-12-11 17:08 ` [PATCH 07/13] trace-cmd: Remove making of ld.so.conf.d/trace.conf Steven Rostedt
2020-12-11 17:08 ` [PATCH 08/13] trace-cmd: Install libtracecmd in the proper lib directory Steven Rostedt
2020-12-11 17:08 ` [PATCH 09/13] trace-cmd: Move the installing of libtracecmd to the lib/trace-cmd Makefile Steven Rostedt
2020-12-11 17:08 ` [PATCH 10/13] trace-cmd: Install the soft links for libtracecmd.so Steven Rostedt
2020-12-11 17:08 ` [PATCH 11/13] trace-cmd: Do not install libtracefs nor libtraceevent libraries Steven Rostedt
2020-12-11 17:08 ` [PATCH 12/13] trace-cmd: Do not build shared libraries for libtracefs and libtraceevent Steven Rostedt
2020-12-11 17:08 ` [PATCH 13/13] trace-cmd: Add warning if libtracefs or libtraceevent are not found 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=20201211170842.611554918@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@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).