This changes the clang-tidy script to discover binaries you've built
locally without having to pass them. This behavior currently depends on
python3, which based on a recent mailing list conversation, sounds like
an ok change.
Details
- Reviewers
kastiglione - Commits
- rG5da83eeb91ba: clang-tidy: discover binaries in build dir
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
I like it, though I'm not sure about the python3 requirement.
clang-tools-extra/clang-tidy/tool/run-clang-tidy.py | ||
---|---|---|
183 | s/is not valid/could not be found/ ? also I wonder the message needs both arg and name, wouldn't it be likely that arg contains name? |
As far as the python3 conversation it appears based on this email thread https://lists.llvm.org/pipermail/llvm-dev/2021-January/148229.html and this documentation https://llvm.org/docs/GettingStarted.html#software that python3.6 is now required, so I think this is ok. There might be things relying on this, in which case I assume asking them to upgrade is an acceptable answer at this point.
clang-tools-extra/clang-tidy/tool/run-clang-tidy.py | ||
---|---|---|
183 | Updated the error message, the original reason I went with something this vague is if the binary exists but isn't executable it will also hit this error, now I've added that to the message as well. I agree the name inclusion was an overoptimization |
Ping, it seems like https://reviews.llvm.org/D101037 is stalled but the docs at this point state py >=3.6 is required for working on llvm so I think we're good here https://llvm.org/docs/GettingStarted.html#software
s/is not valid/could not be found/ ?
also I wonder the message needs both arg and name, wouldn't it be likely that arg contains name?