From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Mike Frysinger <vapier@gentoo.org>, newlib@sourceware.org
Subject: Re: [RFC/PATCH] newlib: enable automatic dependency generation
Date: Thu, 17 Mar 2022 07:25:31 +0100 [thread overview]
Message-ID: <3ecd50ec-f9f4-9cf9-a5ce-52f082c50e50@embedded-brains.de> (raw)
In-Reply-To: <20220317021654.15410-1-vapier@gentoo.org>
On 17/03/2022 03:16, Mike Frysinger wrote:
> This was disabled as part of the migration away from the cygnus option
> as that implied no-dependencies.
>
> We currently have 1-to-1 updates enabled -- if you touch a .c file,
> the corresponding .o file will be rebuilt. But if you touch a header
> file, none of the files using that get rebuilt.
>
> Not sure how much we care. I think we want this since it's probably
> what people are expecting. It increases the size of the Makefile a
> bit, and adds a little build overhead to generate & process.
I think the proper dependency tracking should be enabled. This helps
everyone doing changes in Newlib. The dependency files generated by GCC
are also sometimes helpful to figure out what is actually used to build
a file.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-03-17 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 2:16 Mike Frysinger
2022-03-17 6:25 ` Sebastian Huber [this message]
2022-03-17 9:49 ` Corinna Vinschen
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=3ecd50ec-f9f4-9cf9-a5ce-52f082c50e50@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).