File: install.md

package info (click to toggle)
ccache 4.13.2-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 5,420 kB
  • sloc: cpp: 50,251; asm: 28,570; sh: 9,632; ansic: 5,357; python: 834; perl: 68; makefile: 24
file content (131 lines) | stat: -rw-r--r-- 3,987 bytes parent folder | download
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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
# Ccache installation

## Prerequisites

**Required:**

- CMake 3.15 or newer
- A C++20 compiler (see [Supported platforms, compilers and
  languages](https://ccache.dev/platform-compiler-language-support.html) for
  details)
- A C99 compiler
- Software libraries listed in _Dependencies_ below

**Optional:**

- [Bash](https://www.gnu.org/software/bash) and [Python](https://www.python.org)
  to run the test suite
- [Asciidoctor](https://asciidoctor.org) to build documentation in HTML and
  Markdown formats
- [Pandoc](https://pandoc.org) to build documentation in Markdown format

See also [CI configurations](../.github/workflows/build.yaml) for regularly
tested build setups, including cross-compilation and dependencies required in
Debian/Ubuntu environments.

## Software library dependencies

### How to locate or retrieve dependencies

The CMake variable `DEPS` can be set to select how software library dependencies
should be located or retrieved:

- `AUTO` (default): Use dependencies from the local system if available,
  otherwise use bundled dependencies if available, otherwise download
  dependencies from the internet (dependencies will then be linked statically)
- `DOWNLOAD`: Use bundled dependencies if available, otherwise download
  dependencies from the internet (dependencies will then be linked statically)
- `LOCAL`: Use dependencies from the local system if available, otherwise use
  bundled dependencies if available

### Dependencies

**Required libraries:**

- [BLAKE3](https://github.com/BLAKE3-team/BLAKE3)[^1]
- [fmt](https://fmt.dev)[^1]
- [tl-expected](https://github.com/TartanLlama/expected)[^1]
- [xxhash](https://github.com/Cyan4973/xxHash)[^2]
- [Zstandard](https://github.com/facebook/zstd)[^2]

**Optional libraries:**

- [cpp-httplib](https://github.com/yhirose/cpp-httplib)[^1] (disable with `-D
  HTTP_STORAGE_BACKEND=OFF`)
- [doctest](https://github.com/doctest/doctest)[^2] (disable with `-D
  ENABLE_TESTING=OFF`)
- [hiredis](https://github.com/redis/hiredis)[^2] (disable with `-D
  REDIS_STORAGE_BACKEND=OFF`)

[^1]: A bundled version will be used if missing locally.
[^2]: A downloaded version will be used if missing locally.

### Configuration tips

- To make CMake search for libraries in a custom location, use `-D
  CMAKE_PREFIX_PATH=/some/custom/path`.
- To link libraries statically, pass `-D STATIC_LINK=ON` to CMake (this is the
  default on Windows). Alternatively, use `-D
  EXAMPLE_LIBRARY=/path/to/libexample.a` to link statically with a specific
  library.

## Installation

### Basic build and installation

Here is the typical way to build and install ccache:

```bash
mkdir build
cd build
cmake -D CMAKE_BUILD_TYPE=Release ..
make
make install
```

### Common configuration options

- Set the installation directory (e.g., to `/usr`): add `-D
  CMAKE_INSTALL_PREFIX=/usr`
- Set the system configuration file location (e.g., to `/etc`): add `-D
  CMAKE_INSTALL_SYSCONFDIR=/etc`

### Using ccache

There are two different ways to use ccache to cache compilations:

#### Method 1: Prefix compilation commands with ccache

This method is most convenient if you want to try out ccache or use it for
specific projects only.

```bash
ccache gcc -c hello.c
ccache g++ -c hello.cpp
```

#### Method 2: Let ccache masquerade as the compiler

This method is most useful when you want ccache to automatically cache all your
compilations. Ccache will intercept compiler calls and handle caching
transparently.

On platforms with symbolic link support:

```bash
cp ccache /usr/local/bin/
ln -s ccache /usr/local/bin/gcc
ln -s ccache /usr/local/bin/g++
```

On platforms without symbolic link support, simply copy ccache to the compiler
name:

```bash
cp ccache /usr/local/bin/gcc
cp ccache /usr/local/bin/g++
```

**Important:** The directory containing the ccache symbolic links or copies
(e.g., `/usr/local/bin`) must come before the directory with the actual compiler
(typically `/usr/bin`) in your `PATH` environment variable.