From: Tom Rini <trini@konsulko.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: Compile only changed files when doing 'make'?
Date: Tue, 25 Jan 2022 12:34:51 -0500 [thread overview]
Message-ID: <20220125173451.GB7515@bill-the-cat> (raw)
In-Reply-To: <ssp68j$bos$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Tue, Jan 25, 2022 at 03:50:43PM -0000, Grant Edwards wrote:
> I'm working on a Renesas supplied port of U-Boot, and it seems that
> 'make' always compiles every single (configured) source file instead
> compiling only the source files that have been changed since the
> previous 'make'. I've never run into this before on projects that use
> 'make', and it makes development of U-Boot rather grueling.
>
> Is that due to something Renesas broke?
>
> Or is that a "feature" of the standard U-Boot Makefile?
So, it partly depends on what version of U-Boot that you're working on
top of. It's still to me a relatively recent set of improvements that
fix a number of reproducible build changes and so that with a constant
SOURCE_DATE_EPOCH nothing is rebuilt that hasn't changed, and so it's
also true that re-running "make" only rebuilds the few files that would
change due to time stamp usage, which has also been corrected.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-25 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:50 Compile only changed files when doing 'make'? Grant Edwards
2022-01-25 17:34 ` Tom Rini [this message]
2022-01-26 15:09 ` Grant Edwards
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=20220125173451.GB7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=grant.b.edwards@gmail.com \
--cc=u-boot@lists.denx.de \
/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