3 ms·
> in-memory compilation cache I'd like to see a persistent cache. In-memory doesn't work well for the "occasionally recompile Firefox, LLVM/clang, WebKitGTK, e
by floatboth 8y ago
> in-memory compilation cache
I'd like to see a persistent cache. In-memory doesn't work well for the "occasionally recompile Firefox, LLVM/clang, WebKitGTK, etc." desktop use case...
- lorenzhs 8y agoIsn't that what ccache provides? Admittedly it's not perfect but it sounds like it might help your use case. https://ccache.samba.org https://ccache.samba.org
- AstralStorm 8y agoNo, it is close to what LTO, parse caches and precompiled headers provide. No need for daemons to get the same result.
- floatboth 8y agoThis new zapcc thing seems to be more granular than ccache, it caches individual template instantiations
- elteto 8y agoBazel is exactly this (and amazingly good at it), a cache of your entire build tree and all its dependencies. But it is a full blown build system that you need to buy into. You can’t bolt it on to whatever you are using like ccache.
- floatboth 8y agoThis new zapcc thing seems to be more granular than ccache, it caches individual template instantiations. Bazel can't do that.
- jingwen 8y agoBazel supports persistent compilers with its worker protocol [0]. It's already supported for javac. It may be worthwhile to investigate how well zapcc can integrate with Bazel. [0] https://blog.bazel.build/2015/12/10/java-workers.html https://blog.bazel.build/2015/12/10/java-workers.html