#clang-format

[fuscusamongus]

clang-format

Having ported my projects and workflows to cmake based CLion I’m trying to add some more automation to the development and building process. Today I managed to integrate 2 awesome tools into the process.

cppcheck

clang-format

Both can be installed via homebrew and configuration is fairly simple, assuming you want to use some predefined style. For your own set of rules the configuration might be a bit more complex. 

Here’s how my CMakeLists.txt entries look like:

add_custom_target(cppcheck        WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}        COMMAND /usr/local/bin/cppcheck        --enable=warning,performance,portability,information,missingInclude        --std=c++11        --library=qt.cfg        --template="[{severity}][{id}] {message} {callstack} \(On {file}:{line}\)"        --verbose        --quiet ${SOURCE_FILES}        ) add_custom_target(clangformat        WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}        COMMAND /usr/local/bin/clang-format -style=WebKit -i ${SOURCE_FILES})

[clandestinecoder]

Reusing the default .clang-format configuration file from the ‘atom-format‘ package

I wanted to try using VS Code for a bit instead of Atom. The default clang format settings in VS Code differed from the defaults used by the ‘atom-format‘ package in Atom, which is what I’ve used up until this point. I wanted to use the same formatting behavior in both environments so that I can freely switch between the two in the future as needed.

Turns out the configuration settings for the atom-format package are readily accessible in the “Config Folder“. Once in settings, select the “Open Config Folder“ button. After the second atom window opens in the root of the ‘.atom’ folder, navigate to packages/atom-format. The .clang-format file therein may be copied and placed in the root directory of the project of interest for reutilization within VS Code; the file is read and used automatically by VS Code.