I guess that the simple answer is that ccache is great when the build system is broken (i.e. the dependencies are not correctly tracked, and to get everything built correctly you might need make clean; make). On the other hand, if dependencies are correctly tracked, then ccache will not yield any advantage over plain make, and will actually incur the cost of maintaining the cache and updating it (the size of the cache might be huge depending on the size of the project)
I guess that the simple answer is that
ccache
is great when the build system is broken (i.e. the dependencies are not correctly tracked, and to get everything built correctly you might needmake clean; make
). On the other hand, if dependencies are correctly tracked, thenccache
will not yield any advantage over plainmake
, and will actually incur the cost of maintaining the cache and updating it (the size of the cache might be huge depending on the size of the project)