Hi! Thanks so much for all your detailed and helpful answers! On Sat, Dec 5, 2020 at 3:30 PM Joel Rosdahl wrote: > On Thu, 3 Dec 2020 at 11:28, Steffen Dettmer wrote: > > a "plug-in replacement"? > > Yes to all instances of the question. > Wow, I didn't hope that it could be that great!
Hi, On Sun, Aug 2, 2020 at 6:55 PM Christian Ledergerber via ccache < email@example.com> wrote: > for our builds currently clang-tidy is currently the limiting factor in > terms of speed. > > There is one utility out there which tries to cache the output of > clang-tidy, however it seems to
Hi, in short: Is upgrading to ccache 4 a "drop-in replacement" even if sharing the cache directory with still running ccache 3 versions? in detail: I consider upgrading to ccache 4 with or without sharing the cache directory with older ccache (~3.7.7). Sharing the directory could ease migration
Hi, about half a year ago I started adding ccache to the proprietary toolchains at my workplace. I met several challenges (difficult environments) but I got so much help from Joel Rosdahl and others that they could be solved. I'm so glad that I added it, it works so fine now and saves so much!
Hi, thank you so much for your so valuable input!! On Sat, Mar 21, 2020 at 2:19 PM Joel Rosdahl wrote: > > On Tue, 17 Mar 2020 at 10:06, Steffen Dettmer via ccache > wrote: > > As workaround for a special unrelated issue currently we redefine > > __FILE__ (and try to rem
Hi, * On Tue, Mar 17, 2020 at 3:54 PM Paul Smith wrote: > You don't say which compiler you're using but if you're using GCC you > can consider using the -ffile-prefix-map option to avoid these issues. Thanks for the tip! Your are right, this is for gcc, sorry that I didn't mention.
Hi, I setup ccache with shared cache for some of our projects and I would like to learn how to do it correctly. Projects here have 1-2 MLOC in 3-10k files (mostly C++) and are built via cmake files. We have around 20 devs active typically plus Jenkins and mostly they compile the same inputs