Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] ccache problem when compiling with different toolchains in different projects
Date: Fri, 19 Apr 2013 22:54:51 +0200	[thread overview]
Message-ID: <5171AF1B.4010806@mind.be> (raw)
In-Reply-To: <CADzL+YjA_Zx0BCmWESKYnna=dGyf=3BY9pd00m-BhAbw-HG9TQ@mail.gmail.com>

On 19/04/13 13:41, Mathias De Mar? wrote:
>
> wouldn't an alternative possibility be to change the CCACHE_COMPILERCHECK to:
> export CCACHE_COMPILERCHECK=%compiler% -v
>
> You don't rely on the timestamp that way, but you still have a check. I
> believe this resolves the clearing of ccache also (see also
> http://lists.busybox.net/pipermail/buildroot/2012-March/051187.html ).

  That sounds like a very good idea!

  It still has a few shortcomings, but it's definitely better than the 
current situation. At least the following are not solved yet.

- Options included in the external toolchain wrapper are not included. 
For instance, if you switch to Thumb on the Sourcery ARM toolchain, that 
will be recorded in the additional cflags in the wrapper and won't be 
visible to ccache.

- The output of gcc -v contains the absolute path, so if you change the 
output directory (or share the ccache between several developers) it 
won't work. But it would be feasible to strip off the $(O) part.

- For internal/crosstool-NG toolchains, when toolchain parameters are 
changed this is still not detected. For instance, some configure script 
checks for wchar, it fails, you change your configuration to include 
WCHAR and rebuild, and it still fails because the cached test is used...


  The ideal is still what I mentioned a year ago [1]: make a hash of the 
toolchain configuration part of the buildroot config. Too complex, unless 
we do a big rename of the relevant options into BR2_TOOLCHAIN_...
and grep them out of the config.


  Regards,
  Arnout


[1]
    http://lists.busybox.net/pipermail/buildroot/2012-February/049998.html

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-04-19 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  1:50 [Buildroot] ccache problem when compiling with different toolchains in different projects Danomi Manchego
2013-04-19 11:41 ` Mathias De Maré
2013-04-19 20:54   ` Arnout Vandecappelle [this message]
2013-04-19 23:00     ` Danomi Manchego
2013-04-19 23:05       ` Danomi Manchego
2013-04-19 23:41       ` Arnout Vandecappelle
2013-04-20 16:08         ` Danomi Manchego
2013-04-21 21:05           ` Mathias De Maré
2013-04-22  5:59           ` Arnout Vandecappelle
2013-04-22 12:32             ` Danomi Manchego
2013-04-22 21:26               ` Arnout Vandecappelle
2013-10-24 10:31                 ` Thomas De Schampheleire
2013-10-24 14:55                   ` 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=5171AF1B.4010806@mind.be \
    --to=arnout@mind.be \
    --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