From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 1/2] kernel-shark: Do not hard-code app name
Date: Mon, 11 Apr 2022 18:17:43 +0300	[thread overview]
Message-ID: <20220411151744.445930-1-y.karadz@gmail.com> (raw)
Instead, use 'cmakedefine' the export the corresponding Cmake
build variable.
Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
---
 build/deff.h.cmake  | 3 +++
 src/kernelshark.cpp | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/build/deff.h.cmake b/build/deff.h.cmake
index 82379df..4302f00 100644
--- a/build/deff.h.cmake
+++ b/build/deff.h.cmake
@@ -11,6 +11,9 @@
 /** KernelShark Version number. */
 #cmakedefine KS_VERSION_STRING "@KS_VERSION_STRING@"
 
+/** KernelShark Application name. */
+#cmakedefine KS_APP_NAME "@KS_APP_NAME@"
+
 /** KernelShark installation prefix path. */
 #cmakedefine _INSTALL_PREFIX "@_INSTALL_PREFIX@"
 
diff --git a/src/kernelshark.cpp b/src/kernelshark.cpp
index c373f54..1ad15f4 100644
--- a/src/kernelshark.cpp
+++ b/src/kernelshark.cpp
@@ -56,7 +56,7 @@ int main(int argc, char **argv)
 	int c;
 
 	QApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
-	QApplication::setDesktopFileName("kernelshark");
+	QApplication::setDesktopFileName(KS_APP_NAME);
 	QApplication a(argc, argv);
 
 	KsMainWindow ks;
-- 
2.32.0
next             reply	other threads:[~2022-04-11 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 15:17 Yordan Karadzhov (VMware) [this message]
2022-04-11 15:17 ` [PATCH 2/2] kernel-shark: Fix memory corruption in KsCaptureDialog 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=20220411151744.445930-1-y.karadz@gmail.com \
    --to=y.karadz@gmail.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).