From: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx>
A make clean should clean up the cmake files as well.
Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
---
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
|