From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] ccache: change compilercheck to use compiler and toolchain info
Date: Thu, 28 Nov 2013 23:20:35 +0100 [thread overview]
Message-ID: <87a9goxj64.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <528D33E5.2080004@mind.be> (Arnout Vandecappelle's message of "Wed, 20 Nov 2013 23:12:53 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
[Nice overview snipped]
> One more option is to always generate a wrapper, also for the
> internal toolchain. That one can set CCACHE_EXTRAFILES to a file that
> contains the toolchain options, and set CCACHE_COMPILERCHECK to
> none. The external toolchain wrapper could similarly be extended to
> call ccache instead of the compiler - and then it can just use
> mtime. And for the host compiler nothing needs to be done, it can just
> default to mtime.
I'm starting to think this is the best approach, yes.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-11-28 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 2:54 [Buildroot] [PATCH 0/3] ccache compilercheck and automated option setup Danomi Manchego
2013-10-31 2:54 ` [Buildroot] [PATCH 1/3] ccache: change compilercheck to use compiler and toolchain info Danomi Manchego
2013-11-20 22:12 ` Arnout Vandecappelle
2013-11-28 22:20 ` Peter Korsgaard [this message]
2013-10-31 2:54 ` [Buildroot] [PATCH 2/3] ccache: change default cache directory path to match config setting Danomi Manchego
2013-10-31 2:54 ` [Buildroot] [PATCH 3/3] ccache: provide capability to do initial ccache setup Danomi Manchego
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=87a9goxj64.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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