-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 28 September 2002 02:07, you wrote: > Basically, it competes with make for > dependency tracking. It seems to try to do it in a smart way, but > having two tools trying to outsmart each other seeds doubt in my mind. > This doubt may have no foundation whatsoever, just unsubstantiated gut > feeling.
Totally wrong. The basic premise of ccache is the following: IF YOU RUN THE SAME COMPILER ON THE SAME SOURCE YOU SHOULD GET THE SAME OBJECT FILE. If you think that this does not take H files into consideration you are wrong. As Muli rightly states ccache takes the output of gcc -M which means the ENTIRE source that the compiler sees (H files and all AFTER preprocessor). In addition, it also stores the flags used for the compilation in the cache. I would rarely see a situation where you would say that YOU DO want the object recompiled unless you switched compilers (I'm not sure but I think that there are plans for ccache to store the compiler version too so if you switch compilers it will detect it and not use the cache. Muli ?!?). ccache has NOTHING to do with dependency tracking. It is a compiler wrapper. Think of it as adding a cache to gcc. Mark. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9lO6pxlxDIcceXTgRAqUOAKCngdxaQDaidaSJYRvLHwsrTG32kwCgkS0E 9OX2bE5KbzLwBy64rLQUS0Y= =AME7 -----END PGP SIGNATURE----- ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
