From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: Yordan Karadzhov <y.karadz@gmail.com>, Troy Engel <troyengel@gmail.com>
Subject: [PATCH v2 2/3] kernel-shark: Have "make clean" run cmake-clean.sh
Date: Thu, 27 Jun 2019 13:05:55 -0400 [thread overview]
Message-ID: <20190627170733.133714152@goodmis.org> (raw)
In-Reply-To: 20190627170553.050679238@goodmis.org
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
A make clean should clean up the cmake files as well.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
Makefile | 1 +
kernel-shark/README | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 693f33b69b4e..c9679d42fdbd 100644
--- a/Makefile
+++ b/Makefile
@@ -357,6 +357,7 @@ clean:
$(MAKE) -C $(src)/python clean
$(MAKE) -C $(src)/tracecmd clean
if [ -f $(kshark-dir)/build/Makefile ]; then $(MAKE) -C $(kshark-dir)/build clean; fi
+ cd $(kshark-dir)/build; ./cmake_clean.sh
##### PYTHON STUFF #####
diff --git a/kernel-shark/README b/kernel-shark/README
index 7155e13b17fc..b133f1848fd2 100644
--- a/kernel-shark/README
+++ b/kernel-shark/README
@@ -49,7 +49,7 @@ changed by passing in "prefix" to the build.
make prefix=/usr gui
2.1.1.2 Use "make clean" if you want to delete all already compiled objects.
-Note, this will not clean up the files created by cmake. See section 2.1.2.4
+This will also clean up all the files created by cmake.
2.1.2 Option 2 (expert) : standalone build of KernelShark (for hackers only)
--
2.20.1
next prev parent reply other threads:[~2019-06-27 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 17:05 [PATCH v2 0/3] kernel-shark: Make some top level "make" changes and documention updates Steven Rostedt
2019-06-27 17:05 ` [PATCH v2 1/3] kernelshark: Update the README for changes to the make process Steven Rostedt
2019-06-27 17:05 ` Steven Rostedt [this message]
2019-06-27 17:05 ` [PATCH v2 3/3] kernel-shark: Add make BUILD_TYPE=X gui to change how the gui is made Steven Rostedt
2019-06-28 13:26 ` Yordan Karadzhov (VMware)
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=20190627170733.133714152@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=troyengel@gmail.com \
--cc=y.karadz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.