I just found out about the ccache tool. It's a tool that sits in front of gcc and caches the results of each compile, so that subsequent builds go a lot faster. I've been rebuilding my sources over and over today, trying to get code coverage to work, and it has come in handy. Unfortunately, it doesn't yet support gcc's code coverage features, because it doesn't realize that it needs to cache the *.bb and *.bbg files that gcc generates -- instead, it only caches the object file. It's still useful, though.
Followups to ccache:Posted on March 2, 2004 05:24 PM
More programming articles
Yeah, ccache is great. You might also like to check out colormake, valgrind, libsafe, the boehm garbage collector, and their various offspring and variants. Lots of useful tools out there.
Thanks for the list. I already knew about valgrind and the boehm gc, and I've been using a homegrown version of colormake for quite a while (built on a colorizing grep that I wrote). However I hadn't heard of libsafe before. It's an interesting idea.
Posted by: Kim at March 3, 2004 11:56 AMI've had endless problems with ccache, though it might just be with Gentoo's particular way of installing it. I use it and suddenly things don't link that used to. Seems that it caches too liberally. But it's good that it's working for you.
And I had no idea gcc had code coverage features. Neat.
Posted by: Luke at March 5, 2004 12:05 AMA couple other interesting bits: gcc has support for precompiled headers. This is available on the 3.4 branch in CVS. Vesta supports caching as well as lots of other stuff. Overvew of vesta. KCachegrind and calltree a pretty nice too if you are using valgrind.
Posted by: at March 5, 2004 04:02 AM