From: Yordan Karadzhov <ykaradzhov@vmware.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
"y.karadz@gmail.com" <y.karadz@gmail.com>,
"troyengel@gmail.com" <troyengel@gmail.com>,
Yordan Karadzhov <ykaradzhov@vmware.com>
Subject: [PATCH v2 0/3] KernelShark build fixes for v1.0
Date: Fri, 14 Jun 2019 13:26:46 +0000 [thread overview]
Message-ID: <20190614132609.16465-1-ykaradzhov@vmware.com> (raw)
Patches addressing the problem of having the paths to the build
directory embedded in the final binaries. The problem was reported
by Troy Engel.
Changes in v2:
- In FindTraceCmd.cmake : discovering the trace-cmd executable is now
a compulsory requirement.
- A new buld type called "Package" has been defined.
Yordan Karadzhov (3):
kernel-shark: Remove the "-g" compiler flag.
kernel-shark: Avoid TRACECMD_BIN_DIR being set to the build path
kernel-shark: Define a CMAKE_BUILD_TYPE "Package"
kernel-shark/CMakeLists.txt | 45 ++++++++++++++++++---------
kernel-shark/README | 22 +++++++++----
kernel-shark/build/FindTraceCmd.cmake | 18 ++++++-----
kernel-shark/build/deff.h.cmake | 2 +-
kernel-shark/src/KsCaptureDialog.cpp | 7 ++---
5 files changed, 61 insertions(+), 33 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-14 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:26 Yordan Karadzhov [this message]
2019-06-14 13:26 ` [PATCH v2 1/3] kernel-shark: Remove the "-g" compiler flag Yordan Karadzhov
2019-06-14 13:26 ` [PATCH v2 2/3] kernel-shark: Avoid TRACECMD_BIN_DIR being set to the build path Yordan Karadzhov
2019-06-14 13:26 ` [PATCH v2 3/3] kernel-shark: Define a CMAKE_BUILD_TYPE "Package" Yordan Karadzhov
2019-07-05 23:34 ` Steven Rostedt
2019-07-08 9:16 ` 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=20190614132609.16465-1-ykaradzhov@vmware.com \
--to=ykaradzhov@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).