From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org, hongzhan.chen@intel.com,
jan.kiszka@siemens.com
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [RFC PATCH 0/2] Allow GUI plugins to build standalone
Date: Wed, 19 Jan 2022 14:02:27 +0200 [thread overview]
Message-ID: <20220119120229.68627-1-y.karadz@gmail.com> (raw)
Hi Hongzhan and Jan,
I tried to build your plugin standalone and I realized that this is
in fact not possible due to some missing header files. This gets fixed
in the following patch-set. I also made some minor modifications in
the code of your plugin and will send you this modified version of
the plugin in a separate email.
Please let me know if you find this modifications useful or not?
Cheers,
Yordan
Yordan Karadzhov (VMware) (2):
kernel-shark: Add KsPluginsGUI.hpp/.cpp
kernel-shark: Install missing headers
src/CMakeLists.txt | 12 ++++++++++++
src/KsPluginsGUI.cpp | 27 +++++++++++++++++++++++++++
src/KsPluginsGUI.hpp | 22 ++++++++++++++++++++++
src/plugins/CMakeLists.txt | 4 ++++
4 files changed, 65 insertions(+)
create mode 100644 src/KsPluginsGUI.cpp
create mode 100644 src/KsPluginsGUI.hpp
--
2.32.0
next reply other threads:[~2022-01-19 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 12:02 Yordan Karadzhov (VMware) [this message]
2022-01-19 12:02 ` [RFC PATCH 1/2] kernel-shark: Add KsPluginsGUI.hpp/.cpp Yordan Karadzhov (VMware)
2022-01-19 12:02 ` [RFC PATCH 2/2] kernel-shark: Install missing headers Yordan Karadzhov (VMware)
2022-01-19 12:10 ` [RFC PATCH 0/2] Allow GUI plugins to build standalone Yordan Karadzhov
2022-02-11 5:03 ` Chen, Hongzhan
2022-02-11 12:30 ` Yordan Karadzhov
2022-02-14 1:19 ` Chen, Hongzhan
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=20220119120229.68627-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=hongzhan.chen@intel.com \
--cc=jan.kiszka@siemens.com \
--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).