Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [Yocto] The design document for ccache-native
Date: Fri, 10 Jun 2011 07:34:24 -0700	[thread overview]
Message-ID: <4DF22B70.2090002@mentor.com> (raw)
In-Reply-To: <4DF18783.6050303@gmail.com>

On 06/09/2011 07:54 PM, Khem Raj wrote:
> On 06/09/2011 04:51 PM, Tom Rini wrote:
>> On 06/09/2011 03:40 PM, Saul Wold wrote:
>>> On 06/02/2011 08:11 PM, wenzong fan wrote:
>>>> Hi Folks,
>>>>
>>>> Please help me to review the design document for ccache-native, and
>>>> I also have two questions about it, any answers or suggestions are
>>>> appreciated.
>>>>
>>>> * Feature name: ccache-native
>>>>      Priority: P3; M2
>>>>      Owner: Wenzong Fan
>>>>      Summary: Integrate ccache-native to yocto
>>>>
>>>> * Description:
>>>> Bitbake supports the 'CCACHE Mechanism', but 'ccache' hasn't been
>>>> included by poky/yocto, just add it as a native tool.
>>>>
>>>> * Usage:
>>>> Build ccache as a native tool by default and enable it for speeding
>>>> target packages build.
>>>>
>>>> * Implementation:
>>>> 1) Copy bb file from OE upstream to:
>>>>        meta/recipes-devtools/ccache/
>>>>
>>>> 2) Update bb file to get the latest ccache_3.1.5 and split the single
>>>> bb file to:
>>>>        'ccache_3.1.5.bb', 'ccache.inc'
>>>>
>>>> 3) Enable ccache in the native tools building.
>>>>
>>> You will need to have it be a dependency pretty early on in the build.
>>> Additionally, this is a bit a new part to this task, we want to have the
>>> default CCACHE_DIR for the build default to a directory in TMPDIR
>>> instead of the user's home directory.  This will mean setting an
>>> environment variable somewhere early also.
>>
>> Can we instead veto ccache and remove it from the bitbake docs?  I can't
>> count the number of times I've run into what I can only imagine are
>> ccache conflicts to explain why a random build failure with ccache in
>> use.
> 
> It works on some hosts somewhat reliably and is unpredictable on some as
> you say. I think keeping it optional is probably the right thing but
> making it default may not be a good thing.

I'm pretty sure it's not reliable so much as lucky, but shoving the
cache somewhere else and making it per-recipe makes me less worried.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-06-10 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DE850E8.2050701@windriver.com>
2011-06-09 22:40 ` [Yocto] The design document for ccache-native Saul Wold
2011-06-09 22:51   ` Richard Purdie
2011-06-09 23:51   ` Tom Rini
2011-06-10  2:54     ` Khem Raj
2011-06-10 14:34       ` Tom Rini [this message]
2011-06-10  1:46   ` wenzong fan

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=4DF22B70.2090002@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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