From: Mike Frysinger <vapier@gentoo.org>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: newlib@sourceware.org
Subject: Re: Generate porting.info in build tree rather than source tree
Date: Sat, 29 Oct 2022 19:17:26 +0545 [thread overview]
Message-ID: <Y10raq2js8x+nraS@vapier> (raw)
In-Reply-To: <123f7625-98be-a5ee-40c7-f743dbc326fa@foss.st.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On 28 Oct 2022 17:40, Torbjorn SVENSSON wrote:
> With the recent improvements in the build system by Mike Frysinger, I've
> noticed a minor regression.
this is not new behavior. you can check out newlib-4.1.0 which doesn't
contain any of my build changes and it does the same thing.
> When building newlib, the file libgloss/doc/porting.info is always
> created in the source tree rather than the build tree. Looking at the
> libgloss/Makefile.* files, it appears that this is derived from the
> libgloss/doc/Makefile.inc line:
> info_TEXINFOS += %D%/porting.texi
>
> To my knowledge (no automake wiz...), %D% is a relative path, so I
> suppose the generated path should not use $(srcdir), yet the Makefile.in
> does contain $(srcdir)/doc/porting.info.
>
> Would it be possible to have this porting.info file generated in the
> build tree rather than the source tree to avoid having the source tree
> in a dirty state after a build?
this is WAI. info files are distributed with releases, so it should be
generated in the source tree. this is documented here:
https://www.gnu.org/prep/standards/html_node/Standard-Targets.html#Standard-Targets
> 'info'
> Normally a GNU distribution comes with Info files, and that means the Info
> files are present in the source directory. Therefore, the Make rule for an
> info file should update it in the source directory. When users build the
> package, ordinarily Make will not update the Info files because they will
> already be up to date.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-29 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 15:40 Torbjorn SVENSSON
2022-10-29 13:32 ` Mike Frysinger [this message]
2022-10-29 15:38 ` Torbjorn SVENSSON
2022-10-30 7:12 ` Mike Frysinger
2022-10-31 15:10 ` Torbjorn SVENSSON
2022-11-04 0:29 ` Mike Frysinger
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=Y10raq2js8x+nraS@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=torbjorn.svensson@foss.st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).