Skip to contentSkip to conversation

ccache

DISCUSSION Gary Thomas 5 participants 6 messages Apr 3, 2012 – Apr 12, 2012

lore
Share & tools
lore
#0 lore raw

Why is ccache being used for Poky/Yocto builds? My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite! Is there some way to disable this?, other than not have ccache on my host computer (not an option as it is useful for other builds I do)

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 8 lines · Gary Thomas

Why is ccache being used for Poky/Yocto builds?  My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite!  Is there some way to disable this?, other than not have ccache on my host computer (not an option as it is useful for other builds I do)

I think the default behavior of using ccache when it's installed is extremely bad, and dangerous, in that the ccache object cache is of both limited usefulness, as you say, and the object cache can get corrupted, leading to extremely odd behavior (and it's rarely a place you think to look as a cause). At Mentor we disabled this behavior, and I really, really think we should do so in the default oe-core bitbake.conf.

Signature · 1 line
Christopher Larson
#2 lore raw
Quoted 10 lines · Chris Larson
Quoted 8 lines · Gary Thomas

Why is ccache being used for Poky/Yocto builds? My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite! Is there some way to disable this?, other than not have ccache on my host computer (not an option as it is useful for other builds I do)

Quoted 7 lines

I think the default behavior of using ccache when it's installed is extremely bad, and dangerous, in that the ccache object cache is of both limited usefulness, as you say, and the object cache can get corrupted, leading to extremely odd behavior (and it's rarely a place you think to look as a cause). At Mentor we disabled this behavior, and I really, really think we should do so in the default oe-core bitbake.conf.

It would be nice / cleaner to not build out the hollow ccache directory structure under tmp when ccache isn't installed or being used. Seeing it there under tmp with levels of empty sub directories beneath it is somewhat confusing.

#3 lore raw
Quoted 20 lines · Bob Cochran
Quoted 10 lines · Chris Larson
Quoted 8 lines · Gary Thomas

Why is ccache being used for Poky/Yocto builds? My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite! Is there some way to disable this?, other than not have ccache on my host computer (not an option as it is useful for other builds I do)

Quoted 7 lines

I think the default behavior of using ccache when it's installed is extremely bad, and dangerous, in that the ccache object cache is of both limited usefulness, as you say, and the object cache can get corrupted, leading to extremely odd behavior (and it's rarely a place you think to look as a cause). At Mentor we disabled this behavior, and I really, really think we should do so in the default oe-core bitbake.conf.

Quoted 4 lines

It would be nice / cleaner to not build out the hollow ccache directory structure under tmp when ccache isn't installed or being used. Seeing it there under tmp with levels of empty sub directories beneath it is somewhat confusing.

I'm tempted to move all the ccache stuff into a separate class and then drop the inherit by default.

Patches welcome for 1.3...

Cheers,

Richard

#4 lore raw
In reply to Gary Thomas
Quoted 9 lines · Gary Thomas

Why is ccache being used for Poky/Yocto builds? My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite! Is there some way to disable this?, other than not have ccache on my host computer (not an option as it is useful for other builds I do)

I add following line in the 'local.conf':
CCACHE=""

Signature · 3 lines
Yi Qingliang
[email protected]
https://niqingliang2003.wordpress.com
#5 lore raw
In reply to Gary Thomas
Quoted 6 lines · Gary Thomas

Why is ccache being used for Poky/Yocto builds? My understanding is that it's a win for _rebuilds_ of the same/related files, but there's not a whole lot of that going on.

If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache which is 1.8GB - quite a bite! Is there some way to disable this?,

CCACHE = ""

in a conf file.

Cheers,

Richard