Home / Compare
Where rninja fits your toolchain
These are honest comparisons — the tool rninja replaces, and the compiler caches that overlap from a different angle. Fair rows, real "pick them when" sections, no astroturf.
rninja vs ninja
→The baseline. rninja parses the same build.ninja and mirrors its flags — the difference is the content-addressed cache, the async scheduler, and the optional remote sharing layer bolted on top.
rninja vs sccache
→A different layer of the stack. sccache wraps the compiler (cc, rustc) and caches one compiler invocation. rninja caches whole ninja actions and can skip a graph edge outright. Often you want one; sometimes both.
rninja vs ccache
→The classic C/C++ compiler cache. It caches a single compile; rninja caches whole ninja actions and can skip an edge entirely. They coexist happily — run ccache inside an rninja action.
Still deciding? The how-it-works page explains the cache that makes the difference, and the FAQ answers the adoption questions.