From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: debugedit@sourceware.org
Subject: Re: [PATCH] debugedit: Add manual using help2man
Date: Thu, 29 Apr 2021 20:47:38 +0200 [thread overview]
Message-ID: <1c15ba69edcc67b83e7adcfc879a159da8e20aa5.camel@klomp.org> (raw)
In-Reply-To: <20210429163625.GC24650@altlinux.org>
Hi Dmitry,
On Thu, 2021-04-29 at 19:36 +0300, Dmitry V. Levin wrote:
> > +# Manual pages are generated for dist
> > +dist_man_MANS = debugedit.1
> > +
> > +debugedit.1: tools/debugedit.c $(top_srcdir)/configure.ac
> > + $(MAKE) $(AM_MAKEFLAGS) debugedit$(EXEEXT)
> > + $(HELP2MAN) -N --output=$@ \
> > + --name='debug source path manipulation tool' \
> > + ./debugedit$(EXEEXT)
>
> The usual way of generating debugedit.1 would be to make it depend on
> debugedit$(EXEEXT) instead. Is this written to avoid any attempts to
> regenerate debugedit.1 at build time?
Yes, that is the idea. It is also what the automake manual recommends
because the man page is a generated file that is distributed.
Cheers,
Mark
prev parent reply other threads:[~2021-04-29 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 16:27 Mark Wielaard
2021-04-29 16:36 ` Dmitry V. Levin
2021-04-29 18:47 ` Mark Wielaard [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=1c15ba69edcc67b83e7adcfc879a159da8e20aa5.camel@klomp.org \
--to=mark@klomp.org \
--cc=debugedit@sourceware.org \
--cc=ldv@altlinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).