ccache is a compiler cache. It speeds up recompilation of C/C++ code by caching previous compilations and detecting when the same compilation is being done again. This often results in a significant speedup in common compilations, especially when switching between branches. This page is about using ccache on Mac with clang and ninja build system. If you want to use Xcode, please refer to the old CCacheMac page.
In order to use ccache with clang, you need to use the current git HEAD, since the most recent version (3.1.9) doesn't contain the patch needed for using chromium style plugin.
To install ccache with homebrew, use the following command:
brew install --HEAD ccache
You can also download and install yourself (with GNU automake, autoconf and libtool installed):
git clone git://git.samba.org/ccache.git
cd ccache
./autogen.sh
./configure && make && make install
Make sure ccache can be found in your $PATH.
You can also just use the current released version of ccache (3.1.8 or 3.1.9) and disable chromium style plugin with clang_use_chrome_plugins=0 in your GYP_DEFINES.
We have to set two environment variables (CC and CXX) before calling gclient runhooks or build/gyp_chromium, given you are currently in chromium/src directory:
export CC="ccache clang -Qunused-arguments"
export CXX="ccache clang++ -Qunused-arguments"
Then run:
GYP_GENERATORS="ninja" ./build/gyp_chromium
or
GYP_GENERATORS="ninja" gclient runhooks
(Instead of relying on the clang/clang++ for building chromium in your $PATH, you can also use the absolute path here.)
In build phase, the following environment variables must be set (assuming you are in chromium/src):
export CCACHE_CPP2=yes
export CCACHE_SLOPPINESS=time_macros
export PATH=`pwd`/third_party/llvm-build/Release+Asserts/bin:$PATH
Then you can just run ninja as normal:
ninja -C out/Release chrome
- Configure ccache to use a different cache size with
ccache -M <max size>. You can see a list of configuration options by calling ccache alone. - The default ccache directory is
~/.ccache. You might want to symlink it to another directory (for example, when using FileVault for your home directory).
That's because the Make implementation bundled with XCode Command Line Tools doesn't understand the
-lz kind of dependencies, installing gnu-make from brew and compile it with gmake instead.