1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
# CACHEDIR is the directory where the cachefiles will be stored.
# (default is "$HOME/.compilercache/cache")
# you can always erase those files if you want to.
# they will be rebuilt as needed.
# you can also create a global compilercache directory in your company,
# possibly on NFS. this makes compilation results of a user available
# to all the other users!
# beware! this is an enormous security risk! if multiple users share
# the same cache directory, they MUST trust each other! That's so
# because one user can manipulate compilation results of other users!
# so it's probably better to leave every user with his private cache
# directory!
CACHEDIR="$HOME/.compilercache/cache"
# TEMPDIR is the directory where temporary files will be placed
# (default is "$HOME/.compilercache/temp") you can erase those files,
# when no compilercache instance is currently running. Make sure that
# only trusted users have access to this directory as they can give
# you wrong .o files and can delete all your files via symlink
# attacks, so it's probably better to leave every user with his
# private temporary directory!
TEMPDIR="$HOME/.compilercache/temp"
# SHALLDEBUG can be "yes" or "no"
# (default is "no")
# here you can choose if you want to see the debug messages
# of the cache. if you say "no" you won't even notice the presence
# of the cache. (apart from the speedup)
# be careful with "yes", because a normal compiler won't write debug
# output, so saying "yes" here might break some scripts like
# ./configure scripts which expect certain output behavior
SHALLDEBUG="no"
# LINKOUTPUT can be "yes" or "no"
# (default is "no")
# if you say "yes" here, the resulting output files will be symbolic
# links into the CACHEDIR.
# if you say "no" here, the resulting output files will be copied
# from the CACHEDIR.
# saying "yes" can be an enormous speedup (especially on NFS),
# you are also saving disk space,
# but you must take care of the following things !!!
# please leave LINKOUTPUT=no if you ain't ABSOLUTELY sure that
# the issues presented here do not affect you.
# (that's why default LINKOUTPUT is "no")
# - if your sources are on NFS, but your CACHEDIR is local,
# then for other hosts the object file links are all invalid.
# - if somebody erases files in the CACHEDIR, links will become
# invalid! (but recompilation will rebuild them correctly)
# - a normal compiler creates output files, not output linkfiles
# so the cache does not behave like a normal compiler.
# this should be no problem though.
# - getting a file from the cache will update the modification time of
# all .o files that link into this cacheobject! this will mean useless
# linker runs because make thinks that the .o files have changed.
# it is no harm, just useless operations.
LINKOUTPUT="no"
# PATH is a colon separated list of directories
# (default is "/bin:/usr/bin")
# it has the usual systems meaning. the script will look here for all
# kinds of programs, but NOT for the compiler
PATH="/bin:/usr/bin"
# COMPILERPATH is a colon separated list of directories
# (default is "/bin:/usr/bin")
# compilercache will search for the compiler ONLY in the
# COMPILERPATH directories and NOT in the PATH directories !
COMPILERPATH="/bin:/usr/bin"
# COMPILERNAMES is a space separated list of compiler binary names
# (default is "c++ g++ cc gcc")
# compilercache will only work together with the listed compilers.
# for example you just have to install a link file from c++-3.0 to
# compilercache in the COMPILERCACHEBINDIR directory and compilercache
# will now also run as c++-3.0
COMPILERNAMES="c++ g++ cc gcc"
# COMPILERCACHEBINDIR is the /bin subdirectory of your
# compilercache installation
# (default is "/usr/lib/compilercache")
# you NEED to set this appropriately otherwise the compilercache
# unifier won't be found
COMPILERCACHEBINDIR="/usr/lib/compilercache"
|
