From: Mike Frysinger <vapier@gentoo.org>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: what is the point of bfd/doc/ header generation rules
Date: Thu, 2 Dec 2021 11:44:37 -0500 [thread overview]
Message-ID: <Yaj39XkNd0zO+yzF@vapier> (raw)
In-Reply-To: <YahxOG+en3yQgw1y@squeak.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On 02 Dec 2021 17:39, Alan Modra via Binutils wrote:
> On Wed, Dec 01, 2021 at 11:57:10PM -0500, Mike Frysinger wrote:
> > bfd/doc/ has a few curious files that i can't seem to find docs on or any
> > references to. are they just uncommon maintainer-esque rules ? or are
> > they obsolete things that i can delete ?
> >
> > specifically, what is the point of:
> > $ cd bfd/doc/
> > $ make libbfd.h libcoff.h bfd.h
>
> See the headers rule in bfd/Makefile.am. The above files are made in
> bfd/doc when regenerating bfd/libbfd.h, bfd/libcoff.h, and
> bfd/bfd-in2.h.
ok, but why is it in the doc/ dir to begin with ? doesn't it make more
sense to move all of those rules/logic to the top-level Makefile.am ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-02 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 4:57 Mike Frysinger
2021-12-02 7:09 ` Alan Modra
2021-12-02 16:44 ` Mike Frysinger [this message]
2021-12-02 21:38 ` Alan Modra
2021-12-03 5:33 ` [PATCH 1/2] bfd: move header updates up a directory Mike Frysinger
2021-12-03 5:33 ` [PATCH 2/2] bfd: unify header generation rules Mike Frysinger
2021-12-03 5:43 ` Mike Frysinger
2021-12-03 23:24 ` Alan Modra
2021-12-03 18:27 ` [PATCH 1/2] bfd: move header updates up a directory Tom Tromey
2021-12-04 3:11 ` Mike Frysinger
2021-12-04 18:21 ` Tom Tromey
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=Yaj39XkNd0zO+yzF@vapier \
--to=vapier@gentoo.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.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).