{"id":12161,"date":"2025-07-22T09:35:42","date_gmt":"2025-07-22T07:35:42","guid":{"rendered":"https:\/\/www.basyskom.de\/?p=12161"},"modified":"2025-07-22T09:36:13","modified_gmt":"2025-07-22T07:36:13","slug":"using-clang-format-in-qt-creator","status":"publish","type":"post","link":"https:\/\/www.basyskom.de\/en\/using-clang-format-in-qt-creator\/","title":{"rendered":"Using clang-format in Qt Creator"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The Benefits of Code Formatting<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Enforcing a consistent code style for a code base greatly improves the readability and reduces the potential for merge conflicts when multiple developers work on the same project. While most companies have style guides, the code style is often not enforced automatically and developers must write their code to match the requirements.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The clang-format<\/a> toolset is our go-to option for automatic code formatting because of the easy integration into Qt Creator and its configurability.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Styles<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The clang-format tool supports several built-in style presets. If the style is set to file<\/em>, custom styles are read from a file<\/a> named .clang-format<\/em> or _clang-format<\/em> which must be located in the same directory or a parent directory of the source code location. The closest configuration file always overrides previous files, so subtrees of the project directory structure can use different code styles.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

If the file<\/em> style is used and no file is available, the default behavior of clang-format is to apply a fallback style. To prevent this, the fallback style option must be set to none<\/em>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For new projects without style requirements provided by the customer, we usually recommend the Qt style file<\/a> from the qt5 repository.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Excluding Files and Directories<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

To exclude files, directories or entire subtrees from automatic formatting, clang-format reads a file named .clang-format-ignore<\/a><\/em> which follows the same override logic as .clang-format<\/em>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This comes in handy if out project embeds source code from a git submodule without a .clang-format<\/em> file where automatic formatting might mess up an entire file after one small change. By adding the directory to a .clang-format-ignore<\/em> file residing in the repository under our control, we can prevent automatic formatting from being performed without making changes to the submodule repository and without placing untracked files in its directory.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Due to a bug in clang-format which was fixed in October 2024<\/a>, the way most auto formatting extensions for IDEs (including Qt Creator) call it ignored exclusions from the .clang-format-ignore<\/em> file. The fix is already included in the current clang-format 20 releases.<\/p>

If only versions up to clang-format 19 can be used during development, putting a .clang-format<\/i> file containing the text\u00a0DisableFormat: true<\/i> into the directory to exclude is a viable workaround.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Integration into Qt Creator<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The features of clang-format are available in Qt Creator by enabling the Beautifier<\/a> plugin. This adds a new entry named Beautifier<\/i> to the preferences dialog.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In the General<\/i> tab, the Tool option must be set to ClangFormat<\/i>. We also recommend enabling the Automatic Formatting on File Save<\/i> checkbox to fully automate the formatting process.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"basysKom,\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The ClangFormat<\/i> tab contains a few more settings we need to adapt to our development setup and project requirements.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"basysKom,\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The ClangFormat command<\/em>\u00a0option must be set to the path of the clang-format executable. Depending on the operating system, clang-format is available in the official repositories (most Linux distributions) or must be downloaded and installed (Windows).<\/p>

The predefined style<\/i> should be set to one of the preset styles or the file<\/em> style. We recommend setting the fallback style to none<\/em> in order to avoid unpleasant surprises when opening unrelated projects and files using the same Qt Creator configuration.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

While the Beautifier plugin also provides a way to input the custom style options using the Use customized style<\/i> radio button, we always recommend the file style. This allows checking the code style file(s) into our repository so they can be used by fellow developers without complex setup steps, no matter which development setup they use.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Conclusion<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

With a few clicks, we have enabled automatic code formatting in Qt Creator and never have to think about braces placement, white spaces and breaking long lines ever again. If a file containing changes is saved, it will be formatted automatically according to the options defined in our .clang-format<\/em> file.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

By adding the configuration files to the repository, the code style becomes part of the project and can be applied by most IDEs or by invoking clang-format from the command line.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The steps described above still require some cooperation from all developers. In order to really enforce the code style and to make sure that all developers contributing to the project apply clang-format, it could be a good idea to add a check to the CI pipeline which blocks merge requests if the committed code does not follow the rules of the .clang-format file.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

In this blog you will learn how to set up clang-format with Qt Creator for consistent, automatic code formatting, including custom style files and exclusion rules for subdirectories.<\/p>","protected":false},"author":4,"featured_media":4011,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1,2,8],"tags":[15],"class_list":["post-12161","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemein","category-blog","category-qt","tag-qt"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/posts\/12161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/comments?post=12161"}],"version-history":[{"count":52,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/posts\/12161\/revisions"}],"predecessor-version":[{"id":12234,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/posts\/12161\/revisions\/12234"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/media\/4011"}],"wp:attachment":[{"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/media?parent=12161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/categories?post=12161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.basyskom.de\/en\/wp-json\/wp\/v2\/tags?post=12161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}