mirror of
https://github.com/reactos/ccache.git
synced 2024-12-11 21:24:01 +00:00
- update version to 2.0
- added CCACHE_RECACHE option (suggestion from Ismael Orenstein <ismore@ieg.com.br>)
This commit is contained in:
parent
9fd352be5a
commit
64fc20ee97
5
ccache.1
5
ccache.1
@ -169,6 +169,11 @@ instead\&. The main reason for setting this option is to avoid the
|
||||
update of the modification time on object files that are the result of
|
||||
the same compilation in a different directory\&.
|
||||
.IP
|
||||
.IP "\fBCCACHE_RECACHE\fP"
|
||||
This forces ccache to not use any cached
|
||||
results, even if it finds them\&. New results are still cached, but
|
||||
existing cache entries are ignored\&.
|
||||
.IP
|
||||
.IP "\fBCCACHE_UNIFY\fP"
|
||||
If you set the environment variable CCACHE_UNIFY
|
||||
then ccache will use the C/C++ unifier when hashing the pre-processor
|
||||
|
10
ccache.c
10
ccache.c
@ -384,6 +384,14 @@ static void from_cache(int first)
|
||||
return;
|
||||
}
|
||||
|
||||
/* the user might be disabling cache hits */
|
||||
if (first && getenv("CCACHE_RECACHE")) {
|
||||
close(fd_stderr);
|
||||
unlink(stderr_file);
|
||||
free(stderr_file);
|
||||
return;
|
||||
}
|
||||
|
||||
utime(stderr_file, NULL);
|
||||
|
||||
if (strcmp(output_file, "/dev/null") == 0) {
|
||||
@ -630,7 +638,7 @@ static void process_args(int argc, char **argv)
|
||||
{
|
||||
const char *opts[] = {"-I", "-Iinclude", "-imacros", "-iprefix",
|
||||
"-iwithprefix", "-iwithprefixbefore",
|
||||
"-L", "-D", "-U", "-x", "-MF", "-MT",
|
||||
"-L", "-D", "-U", "-x", "-MF",
|
||||
"-MT", "-MQ", "-isystem", "-aux-info",
|
||||
"--param", "-A", "-Xlinker", "-u",
|
||||
NULL};
|
||||
|
2
ccache.h
2
ccache.h
@ -1,4 +1,4 @@
|
||||
#define CCACHE_VERSION "1.9"
|
||||
#define CCACHE_VERSION "2.0"
|
||||
|
||||
#include "config.h"
|
||||
|
||||
|
@ -144,6 +144,10 @@ instead. The main reason for setting this option is to avoid the
|
||||
update of the modification time on object files that are the result of
|
||||
the same compilation in a different directory.
|
||||
|
||||
dit(bf(CCACHE_RECACHE)) This forces ccache to not use any cached
|
||||
results, even if it finds them. New results are still cached, but
|
||||
existing cache entries are ignored.
|
||||
|
||||
dit(bf(CCACHE_UNIFY)) If you set the environment variable CCACHE_UNIFY
|
||||
then ccache will use the C/C++ unifier when hashing the pre-processor
|
||||
output if -g is not used in the compile. The unifier is slower than a
|
||||
|
@ -137,6 +137,9 @@ directory when creating the compiler output and will do a file copy
|
||||
instead. The main reason for setting this option is to avoid the
|
||||
update of the modification time on object files that are the result of
|
||||
the same compilation in a different directory.
|
||||
<p><p></p><dt><strong><strong>CCACHE_RECACHE</strong></strong><dd> This forces ccache to not use any cached
|
||||
results, even if it finds them. New results are still cached, but
|
||||
existing cache entries are ignored.
|
||||
<p><p></p><dt><strong><strong>CCACHE_UNIFY</strong></strong><dd> If you set the environment variable CCACHE_UNIFY
|
||||
then ccache will use the C/C++ unifier when hashing the pre-processor
|
||||
output if -g is not used in the compile. The unifier is slower than a
|
||||
|
Loading…
Reference in New Issue
Block a user