public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Ricardo B. Marli��re via ltp" <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>, <ltp@lists.linux.it>
Cc: ltp <ltp-bounces+ricardo=marliere.net@lists.linux.it>
Subject: Re: [LTP] [PATCH v3 3/4] Makefile: Update 'doc' target, add 'doc-clean'
Date: Thu, 27 Mar 2025 08:50:33 -0300	[thread overview]
Message-ID: <D8R0YF9GVL4S.276WLTALPPSQ5@suse.com> (raw)
In-Reply-To: <20250324234016.367228-4-pvorel@suse.cz>

On Mon Mar 24, 2025 at 8:40 PM -03, Petr Vorel wrote:
> 'doc' target previously run docparse documentation. Point it to doc/
> directory so that it build sphinx docs. doc/ dir has metadata/ dir as
> dependency, no need to specify it. Call also '.venv' target.
>
> NOTE: it's still possible to avoid virtualenv by calling 'make -C doc'

From the root dir ?

$ make -C doc
make: Entering directory '/mnt/ext/src/linux/ltp/mail/doc'
make -C /mnt/ext/src/linux/ltp/mail/metadata
make[1]: Entering directory '/mnt/ext/src/linux/ltp/mail/metadata'
/mnt/ext/src/linux/ltp/mail/metadata/parse.sh > ltp.json
make[1]: Leaving directory '/mnt/ext/src/linux/ltp/mail/metadata'
if [ -d .venv ]; then . .venv/bin/activate; fi; sphinx-build -b html . html
/bin/sh: line 1: sphinx-build: command not found
make: *** [Makefile:24: all] Error 127
make: Leaving directory '/mnt/ext/src/linux/ltp/mail/doc'

>
> Add 'doc-clean': to remove only generated data (not optional .venv).
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Changes since v2:
> * 'doc' target: call also '.venv' target
> * Add 'doc-clean' target
>
>  Makefile | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 5066789349..0c572248a4 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -169,8 +169,14 @@ INSTALL_TARGETS		+= $(addprefix $(DESTDIR)/$(bindir)/,$(BINDIR_INSTALL_SCRIPTS))
>  
>  $(INSTALL_TARGETS): $(INSTALL_DIR) $(DESTDIR)/$(bindir)
>  
> -.PHONY: doc
> -doc: metadata-all
> +.PHONY: doc doc-clean
> +
> +doc:
> +	$(MAKE) -C $(abs_builddir)/doc .venv
> +	$(MAKE) -C $(abs_builddir)/doc
> +
> +doc-clean:
> +	$(MAKE) -C $(abs_builddir)/doc clean
>  
>  .PHONY: check
>  check: $(CHECK_TARGETS)


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-03-27 11:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 23:40 [LTP] [PATCH v3 0/4] Update doc related Makefile Petr Vorel
2025-03-24 23:40 ` [LTP] [PATCH v3 1/4] doc/Makefile: Remove also metadata/ltp.json Petr Vorel
2025-03-24 23:40 ` [LTP] [PATCH v3 2/4] doc/Makefile: Allow to create and use .venv Petr Vorel
2025-03-25  8:35   ` Andrea Cervesato via ltp
2025-03-25  9:48     ` Petr Vorel
2025-03-27 11:59       ` Andrea Cervesato via ltp
2025-03-27 14:57         ` Petr Vorel
2025-03-27 21:22           ` Andrea Cervesato via ltp
2025-03-24 23:40 ` [LTP] [PATCH v3 3/4] Makefile: Update 'doc' target, add 'doc-clean' Petr Vorel
2025-03-27 11:50   ` Ricardo B. Marli��re via ltp [this message]
2025-03-27 11:54     ` Andrea Cervesato via ltp
2025-03-28  8:56       ` Petr Vorel
2025-03-28  9:12     ` Petr Vorel
2025-03-24 23:40 ` [LTP] [PATCH v3 4/4] doc: Note 'make doc' in the building doc Petr Vorel

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=D8R0YF9GVL4S.276WLTALPPSQ5@suse.com \
    --to=ltp@lists.linux.it \
    --cc=ltp-bounces+ricardo=marliere.net@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=rbm@suse.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