linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <y.karadz@gmail.com>
To: Mircea Cirjaliu <mircea.cirjaliu@yahoo.com>,
	linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernelshark: generate header file in the build directory
Date: Mon, 27 Oct 2025 21:47:49 +0200	[thread overview]
Message-ID: <12ad8a1f-26fd-147b-3ec3-100ab2175964@gmail.com> (raw)
In-Reply-To: <a5350178-93c4-4aad-a503-a622704fe764@yahoo.com>

The patch is applied. Thanks!

Yordan

On 10/24/25 22:58, Mircea Cirjaliu wrote:
> Mixing versioned and generated files will bloat git listings.
> Put KsCmakeDef.hpp together with the rest of the generated files.
> 
> Signed-off-by: Mircea Cirjaliu <mircea.cirjaliu@yahoo.com>
> ---
>   CMakeLists.txt       | 4 ++--
>   build/cmake_clean.sh | 2 +-
>   src/CMakeLists.txt   | 2 +-
>   3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 54ff97c..84215dd 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -129,7 +129,7 @@ else (CMAKE_BUILD_TYPE MATCHES Package)
>   endif (CMAKE_BUILD_TYPE MATCHES Package)
>   
>   include_directories(${KS_DIR}/src/
> -                    ${KS_DIR}/build/src/)
> +                    ${KS_DIR}/build/include/)
>   
>   message("")
>   message(STATUS "C flags      : " ${CMAKE_C_FLAGS})
> @@ -163,7 +163,7 @@ if (_DOXYGEN_DOC AND DOXYGEN_FOUND)
>   endif ()
>   
>   configure_file(${KS_DIR}/build/deff.h.cmake
> -               ${KS_DIR}/src/KsCmakeDef.hpp)
> +               ${KS_DIR}/build/include/KsCmakeDef.hpp)
>   
>   configure_file(${KS_DIR}/build/ks.desktop.cmake
>                  ${KS_DIR}/${KS_APP_NAME}.desktop)
> diff --git a/build/cmake_clean.sh b/build/cmake_clean.sh
> index 67afd6c..2c05d3e 100755
> --- a/build/cmake_clean.sh
> +++ b/build/cmake_clean.sh
> @@ -6,6 +6,7 @@ rm -f CTestTestfile.cmake
>   rm -f DartConfiguration.tcl
>   rm -rf CMakeFiles/
>   rm -rf src/
> +rm -rf include/
>   rm -rf examples/
>   rm -rf tests/
>   rm -rf Testing/
> @@ -14,7 +15,6 @@ rm -f ../lib/*
>   rm ../kernelshark.desktop
>   rm ../libkshark.pc
>   rm ../org.freedesktop.kshark-record.policy
> -rm -f ../src/KsCmakeDef.hpp
>   rm -f CMakeDoxyfile.in
>   rm -f CMakeDoxygenDefaults.cmake
>   rm -rf .qt/
> diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
> index 0643365..da31f8d 100644
> --- a/src/CMakeLists.txt
> +++ b/src/CMakeLists.txt
> @@ -71,7 +71,7 @@ if (OPENGL_FOUND)
>                     "${KS_DIR}/src/libkshark-plot.h"
>                     "${KS_DIR}/src/KsPlotTools.hpp"
>                     "${KS_DIR}/src/KsPlugins.hpp"
> -                  "${KS_DIR}/src/KsCmakeDef.hpp"
> +                  "${KS_DIR}/build/include/KsCmakeDef.hpp"
>               DESTINATION ${KS_INCLUDS_DESTINATION}
>                   COMPONENT libkshark-devel)
>   

      reply	other threads:[~2025-10-27 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a5350178-93c4-4aad-a503-a622704fe764.ref@yahoo.com>
2025-10-24 19:58 ` [PATCH] kernelshark: generate header file in the build directory Mircea Cirjaliu
2025-10-27 19:47   ` Yordan Karadzhov [this message]

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=12ad8a1f-26fd-147b-3ec3-100ab2175964@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mircea.cirjaliu@yahoo.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).