Kaleidoscope/bin/fix-header-includes

#!/usr/bin/env bash

: "${KALEIDOSCOPE_DIR:=$(pwd)}"
cd "${KALEIDOSCOPE_DIR}" || exit 1

# Process sources first, then headers to minimize errors from removed includes
git ls-files -m | grep -E '\.(cpp|ino)$' | xargs "${KALEIDOSCOPE_DIR}"/bin/iwyu.py
git ls-files -m | grep -E '\.h$' | xargs "${KALEIDOSCOPE_DIR}"/bin/iwyu.py
Improve `include-what-you-use` wrapper script This adds better argument parsing, and more useful options for detecting an analyzing errors. I relies on version >=0.18 of IWYU to work properly, because prior to that its exit codes were non-standard and unhelpful. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com> 2 years ago			`#!/usr/bin/env bash`

			`: "${KALEIDOSCOPE_DIR:=$(pwd)}"`
			`cd "${KALEIDOSCOPE_DIR}" \|\| exit 1`

When running IWYU, process source files before headers Suppose the following: `foo.cpp` refers to the symbol `Bar`, declared in `bar.h`. `foo.h` includes `bar.h`. `foo.cpp` includes `foo.h`, but not `bar.h`. `foo.h` does not refer to any symbols declared in `bar.h`. If we process `foo.h` first, `#include "bar.h"` will be removed, causing IWYU to fail with an error when it tries to process `foo.cpp`, but if we process them in the other order, `foo.cpp` will get that include before it gets removed from `foo.h`. This change sorts the files to be processed, putting all cpp files first, then all header files, minimizing that problem. We could do even better by saving the results from `include-what-you-use` for every file, then going back and calling `fix_includes.py` on each of them, but I don't think it's worth it. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com> 2 years ago			`# Process sources first, then headers to minimize errors from removed includes`
			`git ls-files -m \| grep -E '\.(cpp\|ino)$' \| xargs "${KALEIDOSCOPE_DIR}"/bin/iwyu.py`
			`git ls-files -m \| grep -E '\.h$' \| xargs "${KALEIDOSCOPE_DIR}"/bin/iwyu.py`