>Intersting idea. I have little experience with ccache. It's only useful > from the second time on a package is compiled, right? 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. > > 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? ccache has its own cache of results of compilation of preprocessed C source (depending on compiler version and arguments). It is designed just for situations when $WORKINGDIR is removed before compilations.
According to http://ccache.samba.org/performance.html the first compilation of Samba could be 18% slower with ccache while the second one might be more than 11 times faster.
signature.asc
Description: To jest część wiadomości podpisana cyfrowo
_______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
