public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "Ricardo B. Marlière" <rbm@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 4/5] Makefile: Update 'doc' target, add 'doc-clean'
Date: Mon, 7 Apr 2025 16:53:12 +0200	[thread overview]
Message-ID: <20250407145312.GA101494@pevik> (raw)
In-Reply-To: <D8RV9V5D07EO.ORPMFWGXAMSO@suse.com>

> Hi Petr,

> On Fri Mar 28, 2025 at 6:57 AM -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'

> > Add 'doc-clean': to remove only generated data (not optional .venv).

> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > Changes in v4:
> > * Use 'setup' instead of '.venv' in the top level doc target

> >  Makefile | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)

> > diff --git a/Makefile b/Makefile
> > index 5066789349..6aa77e1b9b 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -170,7 +170,13 @@ INSTALL_TARGETS		+= $(addprefix $(DESTDIR)/$(bindir)/,$(BINDIR_INSTALL_SCRIPTS))
> >  $(INSTALL_TARGETS): $(INSTALL_DIR) $(DESTDIR)/$(bindir)

> >  .PHONY: doc
> > -doc: metadata-all
> > +doc:
> > +	$(MAKE) -C $(abs_builddir)/doc setup
> > +	$(MAKE) -C $(abs_builddir)/doc
> > +
> > +.PHONY: doc-clean
> > +doc-clean:
> > +	$(MAKE) -C $(abs_builddir)/doc clean

> IMO the top-level clean and distclean targets should be responsible of
> calling the respective targets in doc/Makefile, what do you think?

Well, we have in the top level other clean targets:
lib-clean, libs-clean, ac-clean, ac-distclean, ac-maintainer-clean.
Therefore I thought add at least doc-clean would be good. I ignored
doc-distclean.

Most of LTP is compiled and therefore handled by
include/mk/generic_leaf_target.mk. kirk and sparse are special (submodule anyway),
but even they allows to use generic_leaf_target.mk. I'm not sure if I want to
rewrite whole doc/Makefile to support generic_leaf_target.mk, I should, but my
goal was to simplify creating venv. I guess I drop this atm and send v5 and
without it and get to it later.

Kind regards,
Petr

The rest of LTP final directories is handled by
include/mk/generic_leaf_target.mk, but doc/ is somehow special, that's why I
added these targets.

If you call make clean or distclean


> >  .PHONY: check
> >  check: $(CHECK_TARGETS)


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

  reply	other threads:[~2025-04-07 14:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  9:57 [LTP] [PATCH v4 0/5] Update doc related Makefile Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 1/5] doc/Makefile: Remove also metadata/ltp.json Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 2/5] doc: Add sphinx to requirements.txt Petr Vorel
2025-03-28 13:02   ` Andrea Cervesato via ltp
2025-03-31 16:31     ` Petr Vorel
2025-03-31 16:37       ` Petr Vorel
2025-03-31 17:04         ` Andrea Cervesato via ltp
2025-03-31 17:53           ` Petr Vorel
2025-04-01  8:18             ` Andrea Cervesato via ltp
2025-04-01 12:17               ` Petr Vorel
2025-04-01 12:20                 ` Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 3/5] doc/Makefile: Allow to create and use .venv Petr Vorel
2025-03-28 13:05   ` Andrea Cervesato via ltp
2025-03-28  9:57 ` [LTP] [PATCH v4 4/5] Makefile: Update 'doc' target, add 'doc-clean' Petr Vorel
2025-03-28 11:36   ` Ricardo B. Marli��re via ltp
2025-04-07 14:53     ` Petr Vorel [this message]
2025-04-08 19:11       ` Ricardo B. Marli��re via ltp
2025-04-09  8:12         ` Petr Vorel
2025-04-09 12:22           ` Ricardo B. Marli��re via ltp
2025-04-09 13:22             ` Petr Vorel
2025-03-28  9:57 ` [LTP] [PATCH v4 5/5] doc: Note 'make doc' in the building doc Petr Vorel
2025-03-28 13:18 ` [LTP] [PATCH v4 0/5] Update doc related Makefile Andrea Cervesato via ltp

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=20250407145312.GA101494@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --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