xmake-build-cache

Xmake Build Cache (Local & Remote)

Xmake has a built-in compile cache that speeds up rebuilds by reusing object files. Two flavors:

• Local cache — on by default, per-machine, cross-platform (GCC/Clang/MSVC). Replaces ccache for most users.
• Remote cache — a shared server that machines can push/pull objects from. Like Mozilla sccache but cross-platform.

Both use the same --ccache name on the CLI — --ccache= is xmake-speak for "C/C++ build cache", not the ccache tool specifically.

1. Local cache (default)

Enabled automatically. No setup required. Since v2.6.6, xmake uses its own built-in local cache; before that it shelled out to the system ccache.

Toggle

xmake f --ccache=n           # disable for this project
xmake f --ccache=y           # re-enable

Use external ccache instead

If you specifically want the third-party ccache tool (e.g. for CI cache sharing with non-xmake builds):

xmake f --ccache=n --cxx="ccache g++" --cc="ccache gcc"
xmake

Note the --ccache=n — disables xmake's built-in cache so the two don't stack.

Benefits of the built-in cache over external ccache

• Cross-platform. Works on Windows/MSVC; ccache doesn't.
• No subprocess overhead. Xmake does the lookup in-process — no per-file ccache fork.
• Integrated state. Xmake already tracks dependencies, so cache keys are tighter.

Cache location

• Local cache directory: ~/.xmake/cache/ (cross-project shared).
• Clean it:

  xmake g --clean                # nuclear: wipe global cache
  

2. Remote cache service

Shared cache server. First developer to compile uploads objects; everyone else downloads them. Big win for CI + team setups.

Start the server

xmake service --ccache                     # foreground
xmake service --ccache -vD                 # verbose
xmake service --ccache --start             # daemonize
xmake service --ccache --stop
xmake service --ccache --restart

First run creates ~/.xmake/service/server.conf and prints a generated token.