public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: debugedit@sourceware.org
Subject: Re: [PATCH] debugedit: Add manual using help2man
Date: Thu, 29 Apr 2021 19:36:25 +0300	[thread overview]
Message-ID: <20210429163625.GC24650@altlinux.org> (raw)
In-Reply-To: <20210429162722.21085-1-mark@klomp.org>

On Thu, Apr 29, 2021 at 06:27:22PM +0200, Mark Wielaard wrote:
> This generates a debugedit.1 man page using help2man based on the
> debugedit --help output.  The generated file is included in the dist
> so help2man isn't normally needed to build debugedit.
[...]
> diff --git a/Makefile.am b/Makefile.am
> index bd28eba..5042785 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -38,6 +38,15 @@ sepdebugcrcfix_SOURCES = tools/sepdebugcrcfix.c
>  sepdebugcrcfix_CFLAGS = @LIBELF_CFLAGS@ $(AM_CFLAGS)
>  sepdebugcrcfix_LDADD = @LIBELF_LIBS@
>  
> +# 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?


-- 
ldv

  reply	other threads:[~2021-04-29 16:36 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 [this message]
2021-04-29 18:47   ` Mark Wielaard

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=20210429163625.GC24650@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=debugedit@sourceware.org \
    --cc=mark@klomp.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).