Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] Enable ccache for cmake packages
Date: Tue, 12 Mar 2013 22:40:17 +0100	[thread overview]
Message-ID: <513FA0C1.6070404@mind.be> (raw)
In-Reply-To: <20130306195913.2c7e6db7@skate>

On 03/06/13 19:59, Thomas Petazzoni wrote:
> Dear Luca Ceresoli,
>
> On Wed,  6 Mar 2013 18:14:25 +0100, Luca Ceresoli wrote:
>> CMake fails in detecting the compiler when ccache is used. Add a wrapper
>> script to make it happy.
>
> This raises the question of whether we want to generalize this in some
> way: should we be doing the ccache wrapper thing in a generic way, and
> use it everywhere? Since we already have a wrapper for external
> toolchain tools, does it really make sense to have a shell wrapper
> around a C wrapper? Should we have a single C wrapper used in all cases
> (internal, external, crosstool-ng), that handles everything?

  Yes, I would be very much in favour of that. It also solves the issue 
that some configure systems don't deal very well with a CC that contains 
spaces. And for external toolchains, it's nice that the actual options 
that are passed to the external toolchain are also visible to ccache.

  I see two issues however:

- How to deal with HOSTCC?

- How to deal with HOSTCC_NOCCACHE? (TARGET_CC_NOCCACHE can probably be 
removed)


  Anyway, for cmake the solution proposed by Samuel works even better.

  Regards,
  Arnout


> I don't (yet) have a strong opinion on this, I just wanted to have a
> more global reflection about wrappers, and avoid creating many
> wrappers to solve different problems.
>
> Best regards,
>
> Thomas
>


-- 
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-03-12 21:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 17:14 [Buildroot] [PATCH 0/5] CMake packages improvements Luca Ceresoli
2013-03-06 17:14 ` [Buildroot] [PATCH 1/5] cmake: convert spaces to tabs in make rules Luca Ceresoli
2013-03-06 17:53   ` Thomas Petazzoni
2013-03-10 20:27   ` Peter Korsgaard
2013-03-06 17:14 ` [Buildroot] [PATCH 2/5] cmake: remove target package macro (not really implemented) Luca Ceresoli
2013-03-06 17:56   ` Thomas Petazzoni
2013-03-07 16:57     ` [Buildroot] [PATCH v2 2/5] cmake: remove target package macro Luca Ceresoli
2013-03-10 20:28       ` Peter Korsgaard
2013-03-06 17:14 ` [Buildroot] [PATCH 3/5] cmake: bump to 2.8.10.2 Luca Ceresoli
2013-03-10 20:28   ` Peter Korsgaard
2013-03-06 17:14 ` [Buildroot] [PATCH 4/5] Enable ccache for cmake packages Luca Ceresoli
2013-03-06 18:59   ` Thomas Petazzoni
2013-03-12 21:40     ` Arnout Vandecappelle [this message]
2013-03-06 19:02   ` Samuel Martin
2013-03-06 19:52     ` Peter Korsgaard
2013-03-10 20:29     ` Peter Korsgaard
2013-03-12  7:38       ` Luca Ceresoli
2013-03-20 17:15     ` Luca Ceresoli
2013-03-21 22:29       ` Luca Ceresoli
2013-03-22  8:33         ` Samuel Martin
2013-03-22  9:40           ` Luca Ceresoli
2013-03-22 10:08             ` Samuel Martin
2013-03-22 22:41               ` Luca Ceresoli
2013-03-22 22:55                 ` [Buildroot] [PATCH v2] " Luca Ceresoli
2013-03-23  0:03                   ` Samuel Martin
2013-03-23 15:29                     ` Thomas Petazzoni
2013-03-23 17:32                       ` Samuel Martin
2013-03-28 22:21                         ` Luca Ceresoli
2013-03-29 13:08                           ` Samuel Martin
2013-03-06 17:14 ` [Buildroot] [PATCH 5/5] CMake packages: remove .cmake files from target directory Luca Ceresoli
2013-03-10 20:30   ` Peter Korsgaard

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=513FA0C1.6070404@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