>Now, in your case, it sounds like there will be very few .c files that do
>not change, so ccache will not be able to speed up the compilation by
>using already cached .o files.
Can I track which files change every time? I only change one file (for example), so why do other files change?
Do you mean that the developers of this library set some thing (option) in makefile or somewhere else that change timestamp of files?
Mahmood NT
----- Original Message ----
From: Francois Marier <francois at debian.org>
To: Mahmood NT <nt_mahmood at yahoo.com>
Cc: ccache list <ccache at lists.samba.org>
Sent: Saturday, December 8, 2007 12:31:35 PM
Subject: Re: [ccache] how to use ccache
On 2007-12-07 at 23:24:19, Mahmood NT wrote:
> >If your library makes it so that you can't reuse any of the already compiled
> >objects, then ccache is unlikely to make things faster for you.
>> Excuse me but I did not understand. What is the mechanism of ccache?
Simply put, when you compile a .c file, it produces a .o file. ccache keeps
track of the checksum on the .c file and then stores the corresponding .o.
The next time you compile that .c file, if it hasn't changed, it will have
the same checksum and ccache will already have the .o file for it so it
won't have to compile it again.
Now, in your case, it sounds like there will be very few .c files that do
not change, so ccache will not be able to speed up the compilation by
using already cached .o files.
Francois
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ