Lines Matching +full:clang +full:- +full:format +full:- +full:version

8 * [KhronosGroup/Vulkan-Loader](https://github.com/KhronosGroup/Vulkan-Loader)
14 * Examine the [issues list](https://github.com/KhronosGroup/Vulkan-Loader/issues)
40   [forking the repository](https://help.github.com/articles/fork-a-repo/),
42   [submitting a pull request](https://help.github.com/articles/using-pull-requests/).
44   [guidelines](#coding-conventions-and-formatting) enumerated below.
62     The clang-format tool will handle this. See below.
64     Again, the clang-format tool will handle this.
72 * Run **clang-format** on your changes to maintain consistent formatting
73   * There are `.clang-format` files present in the repository to define
74     clang-format settings which are found and used automatically by clang-format.
75   * **clang-format** binaries are available from the LLVM orginization, here:
76     [LLVM](https://clang.llvm.org/).
77     Our CI system currently uses clang-format version 16 to
79     It is recommended that you use the same version to format your code prior
84 >        $ git add -u .
85 >        $ git clang-format --style=file
86 >        # Check to see if clang-format made any changes and if they are OK.
87 >        $ git add -u .
91   * Limit the subject line to 50 characters --
93   * Begin subject line with a one-word component description followed
117 corresponding generated output to keep the repository self-consistent. This requirement is enforced…
119 and testing your changes. More details can be found in [BUILD.md](BUILD.md#generated-source-code).
139   * CMake functions are lower-case.
140   * Variable and keyword names are upper-case.
144 You will be prompted with a one-time "click-through" CLA dialog as part of
149 All contributions made to the Vulkan-Loader repository are Khronos branded