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 1/3] kernelshark: Update the README for changes to the make process
Date: Thu, 27 Jun 2019 13:05:54 -0400 [thread overview]
Message-ID: <20190627170732.991239997@goodmis.org> (raw)
In-Reply-To: 20190627170553.050679238@goodmis.org
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
The top level git tree's Makefile has code added to build the cmake portion
of KernelShark. But the README does not document the process. Bring the
README up to speed with how to actually build KernelShark.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
kernel-shark/README | 50 ++++++++++++++++++++++++++++++++++++---------
1 file changed, 40 insertions(+), 10 deletions(-)
diff --git a/kernel-shark/README b/kernel-shark/README
index 75a0dd08dcac..7155e13b17fc 100644
--- a/kernel-shark/README
+++ b/kernel-shark/README
@@ -30,18 +30,47 @@ Building:
1. Follow the instructions given in trace-cmd/README and build
the original trace-cmd end traceevent libraries.
-2. Do:
- cd kernel-shark/build
- cmake ../
- make
+2. Building KernelShark:
+
+2.1 There is a simple and expert way to build KernelShark
+
+2.1.1 Option 1 (simple) : build KernelShark as part of trace-cmd
+
+ (from the toplevel git tree)
+
+ make gui
+
+ This will build the necessary parts of trace-cmd needed
+ by KernelShark.
+
+2.1.1.1 By default, the installation prefix is "/usr/local". It can be
+changed by passing in "prefix" to the build.
+
+ make prefix=/usr gui
-2.1.1 In order to create a Doxygen documentation add -D_DOXYGEN_DOC=1
+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
+
+2.1.2 Option 2 (expert) : standalone build of KernelShark (for hackers only)
+
+ (note, you may need to do a normal make from the toplevel git
+ tree before performing the following)
+
+ make
+ cd kernel-shark/build
+ cmake ../
+ make
+
+ This gives you a bit more control as you may easily pass in
+ your own cmake options.
+
+2.1.2.1 In order to create a Doxygen documentation add -D_DOXYGEN_DOC=1
as a CMake Command-Line option.
-2.1.2 By default, installation prefix is "/usr/local". It can be changed using
+2.1.2.2 By default, installation prefix is "/usr/local". It can be changed using
-D_INSTALL_PREFIX= as a CMake Command-Line option.
-2.1.3 In addition to the standard CMake build types (Debug, Release,
+2.1.2.3 In addition to the standard CMake build types (Debug, Release,
RelWithDebInfo, MinSizeRel) KernelShark supports a "Package" build type.
By default this build type adds the "-O2" compiler flag. Package maintainers
can chose their own compiler flags by providing the corresponding
@@ -57,10 +86,11 @@ Examples:
cmake -DCMAKE_BUILD_TYPE=Package -DCMAKE_C_FLAGS_PACKAGE="-O3 -pedantic" ../
-2.2.1 Use "make clean" if you want to delete all already compiled objects.
-
-2.2.2 Use the script "cmake_clean.sh" if you want to delete all already
+2.1.2.4 Use the script "cmake_clean.sh" if you want to delete all already
compiled objects and all files generated by CMake.
+ cd kernel-shark/build
+ ./cmake-clean.sh
+
3. After building the code "kernel-shark/lib" will contain all libraries
and "kernel-shark/bin" will contain all executables.
--
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 ` Steven Rostedt [this message]
2019-06-27 17:05 ` [PATCH v2 2/3] kernel-shark: Have "make clean" run cmake-clean.sh Steven Rostedt
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=20190627170732.991239997@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 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).