Re: [ccache] ccache on generated C++ files...

2019-06-25 Thread Malfettone, Kris via ccache
Malfettone, Kris Cc: ccache@lists.samba.org Subject: Re: [ccache] ccache on generated C++ files... On Tue, 25 Jun 2019 at 00:28, Malfettone, Kris via ccache wrote: > So what I seem to be observing is only when I do a ninja -t clean or make > clean. This removes all of my generated files (.

Re: [ccache] ccache on generated C++ files...

2019-06-25 Thread Bernd Petrovitsch via ccache
On 25/06/2019 00:28, Malfettone, Kris via ccache wrote: > So what I seem to be observing is only when I do a ninja -t clean or make > clean. This removes all of my generated files (.h and .cpp files) and of > course the normal build outputs. A subsequent run is then mostly cache > misses. If

Re: [ccache] ccache on generated C++ files...

2019-06-25 Thread Joel Rosdahl via ccache
On Tue, 25 Jun 2019 at 00:28, Malfettone, Kris via ccache wrote: > So what I seem to be observing is only when I do a ninja -t clean or make > clean. This removes all of my generated files (.h and .cpp files) and of > course the normal build outputs. A subsequent run is then mostly cache > misses.

Re: [ccache] ccache on generated C++ files...

2019-06-24 Thread Malfettone, Kris via ccache
Malfettone, Kris Cc: ccache@lists.samba.org Subject: Re: [ccache] ccache on generated C++ files... Hi Kris, On Fri, 21 Jun 2019 at 02:43, Malfettone, Kris wrote: > My project uses a large number of generated C++ files (.h/.cpp files). On a > clean build these files are cleaned up as well. A

Re: [ccache] ccache on generated C++ files...

2019-06-23 Thread Joel Rosdahl via ccache
Hi Kris, On Fri, 21 Jun 2019 at 02:43, Malfettone, Kris wrote: > My project uses a large number of generated C++ files (.h/.cpp files). On a > clean build these files are cleaned up as well. As a result during the next > build since they are generated again they will all have a newer mtime and > c

[ccache] ccache on generated C++ files...

2019-06-20 Thread Malfettone, Kris via ccache
I apologize if this is answered somewhere already however I could not find it. My project uses a large number of generated C++ files (.h/.cpp files). On a clean build these files are cleaned up as well. As a result during the next build since they are generated again they will all have a newer