The rust-based clang-tools-manager is out in the wild now. I'm not sure if it is recommended outside of a CI context though. It uses the following priority to source the clang tools' binaries:
- PyPI releases
- system-native package managers (apt, winget, dnf, homebrew, etc)
- static binaries
And it doesn't currently support clang-query at all, only clang-format and clang-tidy.
- **[clang-tools-manager](https://github.com/cpp-linter/cpp-linter-rs/tree/main/clang-tools-manager)**
- use pre-built binaries with cargo-binstall:
```sh
cargo binstall clang-tools-manager
clang-tools -h
```
- build from source code with cargo
```sh
cargo install clang-tools-manager --locked --features bin
clang-tools -h
```
- clang-tools-manager
- use pre-built binaries with cargo-binstall:
cargo binstall clang-tools-manager
clang-tools -h
- build from source code with cargo
cargo install clang-tools-manager --locked --features bin
clang-tools -h
I suppose I should revise the README for better comprehension first.
Originally posted by @2bndy5 in cpp-linter/.github#82 (comment)
The rust-based
clang-tools-manageris out in the wild now. I'm not sure if it is recommended outside of a CI context though. It uses the following priority to source the clang tools' binaries:And it doesn't currently support clang-query at all, only clang-format and clang-tidy.
I suppose I should revise the README for better comprehension first.
Originally posted by @2bndy5 in cpp-linter/.github#82 (comment)