linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v5] libtraceevent: Add initial support for meson
Date: Wed, 4 Jan 2023 18:10:18 +0100	[thread overview]
Message-ID: <20230104171018.pghozcx2c6wyak72@carbon.lan> (raw)
In-Reply-To: <20230104110128.1cabdf08@gandalf.local.home>

On Wed, Jan 04, 2023 at 11:01:28AM -0500, Steven Rostedt wrote:
> On Wed, 28 Dec 2022 09:29:06 +0100
> Daniel Wagner <dwagner@suse.de> wrote:
> 
> > In case you want to build/install the documentation the setup is
> > 
> >   meson -Ddocs-build=true .build
> > 
> > Signed-off-by: Daniel Wagner <dwagner@suse.de>
> 
> Can we make this so that building docs does not require building the rest
> of the code?

Yes, it could be done by introducing a new target which is not run per
default. Currently, the docs are not added to the build when
'-Ddocs-build=true' is missing.

If I understood you correctly you prefer:

  meson setup .build
  meson compile -C .build
  meson compile -C .build doc

and drop the '-Ddocs-build' option?

  reply	other threads:[~2023-01-04 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  8:29 [PATCH v5] libtraceevent: Add initial support for meson Daniel Wagner
2023-01-04 15:45 ` Steven Rostedt
2023-01-04 17:05   ` Daniel Wagner
2023-01-04 17:31     ` Steven Rostedt
2023-01-04 17:34       ` Steven Rostedt
2023-01-05  7:05         ` Daniel Wagner
2023-01-04 16:01 ` Steven Rostedt
2023-01-04 17:10   ` Daniel Wagner [this message]
2023-01-04 17:32     ` Steven Rostedt

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=20230104171018.pghozcx2c6wyak72@carbon.lan \
    --to=dwagner@suse.de \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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).