Clang not installed when selecting version 14 about cpp-linter-action HOT 5 CLOSED

Reading the workflow's log that you linked in the discussion, it looks like clang-tidy-14 was able to be called and returned a result. Even if that result is undesirable, the fact that the clang-tidy-14 executable was found (& invoked) tells me that it isn't an installation problem.

Have you tried using a compilation database (highly recommended)? This is a rather strict sticking point for clang-tidy (despite the version used).

from cpp-linter-action.

I have updated the docker image clang-tools:all and I can not reproduce this issue anymore.

Currently, this is a temporary solution: just copy the missing *.h files to /usr/include, because keeping llvm-13 and llvm-14 folders in the image will extremely increase the size of the image and cause action to slow down.

from cpp-linter-action.

keeping llvm-13 and llvm-14 folders in the image will extremely increase the size of the image and cause action to slow down.

This is why I've been trying to use the action's src code as an installable python package. The docker image isn't needed if executing the action as a python package, but it does require the end-user to consciously install the desired version of clang-tidy & clang-format (github's actions/cache action can further reduce the setup-time in this scenario). Clearly, this will also require some finesse with the --version arg though.

from cpp-linter-action.

Currently, this is a temporary solution: just copy the missing *.h files to /usr/include

UPDATE: Permanent solution has been done and the docker image has been updated. See cpp-linter/clang-tools-docker#25

from cpp-linter-action.

This issue has been fixed in the latest docker image xianpengshen/clang-tools:all, I'm going to close it.
Please feel free to reopen it in case of any problems.

from cpp-linter-action.