archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <>
To: Zamir SUN <>,
Subject: Re: kernelshark: Proper way to install documents when packaging as rpm
Date: Wed, 12 Oct 2022 19:37:01 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Zamir,

We never had a functional installation of the documentation. The 
documentation itself needs significant amount of work, so I would prefer 
to keep it only as an option for those enthusiasts who want to build the 
project from source.


On 10/11/22 18:15, Zamir SUN wrote:
> Hi,
> When I am working on packaging kernelshark as RPM, I noticed that 
> kernelshark documents cannot be installed with make
> install. My compiling steps is like the following (with the passing of 
> compiling flags omitted in this email to reduce length)
> cd build
> cmake ..  -DCMAKE_BUILD_TYPE=Package -D_DOXYGEN_DOC=1
> make V=1 all doc
> And installation is by
> cd build
> make V=1 install
> Manually running the expanded commands I see there are actually 
> documents compiled under Documentation dir. But the make install did not 
> copy that. `make list_install_components` shows that
> Available install components are: "kernelshark" "libkshark-devel" 
> "polkit-policy"
> Additionally, simply going into Documentation dir and run make install 
> will just result in error
> No rule to make target '/Documentation/kernelshark.1'
> So I feel this isn't the right way either. So I wonder if I should 
> manually copy all the stuff (or a subset?) from Documentation dir into 
> the package, or is there a preferred installation step that I missed?
> Thanks in advance.

  reply	other threads:[~2022-10-12 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 15:15 kernelshark: Proper way to install documents when packaging as rpm Zamir SUN
2022-10-12 16:37 ` Yordan Karadzhov [this message]
2022-10-14 11:32   ` Zamir SUN

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).