All of 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: Mon, 22 Apr 2013 23:26:30 +0200	[thread overview]
Message-ID: <5175AB06.8090101@mind.be> (raw)
In-Reply-To: <CANxTyt7JzGaq0pirMDDUrEn_XTUxK-4CbaPP00Rn0O709eL50w@mail.gmail.com>

On 22/04/13 14:32, Danomi Manchego wrote:
> On Mon, Apr 22, 2013 at 1:59 AM, Arnout Vandecappelle <arnout@mind.be
> <mailto:arnout@mind.be>> wrote:
[snip]
>       Actually, after thinking a bit harder about it: the following
>     should work:
>
>     sed -n '/^# Toolchain/,/^# System configuration/' $(BUILDROOT_CONFIG) \
>              | md5sum -
>
>       So there's no need to rename stuff or anything.
>
>
> That would also use the GDB and ECLIPSE lines too.  But then, if it
> accounts for everything outside of the "%compiler% -v" info (wrappers,
> C-library), then it's worth it.
>
> I suppose that we could drop the these lines with an inverse grep:
>
> sed -n '/^# Toolchain/,/^# System configuration/p' .config | \
>      grep -v -e '^#' -e GDG -e ECLIPSE | \
>      md5sum
>
> Too much?

  Too much, yes :-) But perhaps we could change the order of the 
toolchain options.

  Regards,
  Arnout

-- 
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-22 21:26 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
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 [this message]
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=5175AB06.8090101@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.