|
From: | Sam Geeraerts |
Subject: | Re: [Gnewsense-dev] ccache support patch for the Builder |
Date: | Wed, 16 Jun 2010 20:43:22 +0200 |
User-agent: | Thunderbird 2.0.0.24 (X11/20100402) |
Dmitry Samoyloff schreef:
At Tue, 15 Jun 2010 22:00:46 +0200, Sam Geeraerts wrote:Dmitry Samoyloff schreef:Intersting idea. I have little experience with ccache. It's only useful from the second time on a package is compiled, right?Hello, As far, as I've rebuilt new Gnash in the Builder several times already, ccache is certainly of help for me. Attached is a small 2-line patch for the Builder to support ccache.Yes.Builder normally compiles a package only once. I'm curious to know what the ccache penalty is. If it makes Builder run a lot longer I'd rather not include it by default.http://ccache.samba.org/performance.html Well, at least we could make it an option in config.local, right?
Alright. I'll take a patch where's it's commented in config with an explanation that it's useful to uncomment it when testing.
I guess ccache only works when the binaries are not removed between compiles. Builder removes $WORKINGDIR every time before building a package. Can you explain how ccache can do its thing then?It stores all info in its own cache (say, ~/.ccache/), thus it is OK to remove a build directory. My do-update time for Gnash decreased from half an hour to several minutes with ccache.
So it needs a few extra GiB of disk space for all the packages we rebuild then. I know some people use(d) Builder on an old spare computer that's a bit tight on disk space. But old computers benefit even more for ccache, so that's a good trade-off.
[Prev in Thread] | Current Thread | [Next in Thread] |