blob: b93c70723e68332be0bcc9ae0e8e4cd892e21d4d (
plain)
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
|
# Contributing to ccache
Want to contribute to ccache? Awesome!
## Asking a question?
There are several options:
1. Ask a question in
[discussions](https://github.com/ccache/ccache/issues/discussions).
2. Post your question to the [mailing
list](https://lists.samba.org/mailman/listinfo/ccache/).
3. Chat in the [Gitter room](https://gitter.im/ccache/ccache).
## Reporting an issue?
Please include at least the following information in your bug report:
1. Which version of ccache you use.
2. Which compiler you use, if applicable.
3. Which operating system you use, if applicable.
4. The problematic behavior you experienced (_actual behavior_).
5. How you would like ccache to behave instead (_expected behavior_).
6. Steps to reproduce the problematic behavior.
Also, consider reading [Effective Ways to Get Help from Maintainers](
https://www.snoyman.com/blog/2017/10/effective-ways-help-from-maintainers).
## Contributing code?
The preferred way is to create one or several pull request with your
proposal(s) on [GitHub](https://github.com/ccache/ccache).
Here are some hints to make the process smoother:
* If you plan to implement major changes it is wise to open an issue on GitHub
(or ask in the Gitter room, or send a mail to the mailing list) asking for
comments on your plans before doing the bulk of the work. That way you can
avoid potentially wasting time on doing something that may need major rework
to be accepted, or maybe doesn't end up being accepted at all.
* Is your pull request "work in progress", i.e. you don't think that it's ready
for merging yet but you want early comments and CI test results? Then create
a draft pull request as described in [this Github blog
post](https://github.blog/2019-02-14-introducing-draft-pull-requests/).
* Please follow the ccache's code style (see the section below).
* Consider [A Note About Git Commit
Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
when writing commit messages.
## Code style
Ccache was written in C99 until 2019 when it started being converted to C++11.
The conversion is a slow work in progress, which is why there is a lot of
C-style code left. Please refrain from doing large C to C++ conversions; do it
little by little.
Source code formatting is defined by `.clang-format` in the root directory. The
format is loosely based on [LLVM's code formatting
style](https://llvm.org/docs/CodingStandards.html) with some exceptions. It's
highly recommended to install
[Clang-Format](https://clang.llvm.org/docs/ClangFormat.html) 6.0 or newer and
run `make format` to format changes according to ccache's code style. Or even
better: set up your editor to run Clang-Format automatically when saving. If
you don't run Clang-Format then the ccache authors have to do it for you.
Please follow these conventions:
* Use `UpperCamelCase` for types (e.g. classes and structs) and namespaces.
* Use `UPPER_CASE` names for macros and (non-class )enum values.
* Use `snake_case` for other names (functions, variables, enum class values, etc.).
* Use an `m_` prefix for non-public member variables.
* Use a `g_` prefix for global mutable variables.
* Use a `k_` prefix for global constants.
* Always use curly braces around if/for/while/do bodies, even if they only
contain one statement.
|
