xref: /openbmc/hiomapd/format-code.sh (revision 0ad17216)
1#!/bin/sh
2
3set -euo
4
5set -x
6
7if [ $# -ge 1 ]
8then
9    cd "$1"
10fi
11
12[ -f .clang-format ] && rm .clang-format
13
14# Use the provided clang-format, only define a version
15# if we don't have one provided already
16export CLANG_FORMAT="${CLANG_FORMAT:-clang-format-11}"
17
18# phosphor-mboxd is a fork of mboxbridge, the reference mbox daemon
19# implementation. mboxbridge is C written with the style of the Linux kernel.
20#
21# phosphor-mboxd extended the reference in C++, and used the OpenBMC C++ style.
22#
23# To remain compliant with the C++ style guide *and* preserve source
24# compatibility with the upstream reference implementation, use two separate
25# styles.
26#
27# Further, clang-format supports describing styles for multiple languages in
28# the one .clang-format file, but *doesn't* make a distinction between C and
29# C++. So we need two files. It gets worse: the -style parameter doesn't take
30# the path to a configuration file as an argument, you instead specify the
31# literal 'file' and it goes looking for a .clang-format or _clang-format file.
32# So now we need to symlink different files in place before calling
33# ${CLANG_FORMAT}. Everything is terrible.
34#
35# ln -sf .clang-format-c .clang-format
36# git ls-files | grep '\.[ch]$' | xargs "${CLANG_FORMAT}" -i -style=file
37
38ln -sf .clang-format-c++ .clang-format
39git ls-files | grep '\.[ch]pp$' | xargs "${CLANG_FORMAT}" -i -style=file
40
41rm .clang-format
42