Closed rjoomen closed 1 month ago
Not clang-tidy, I think, but gcc, because of the warnings-as-errors option. Or is it the ros-industrial-cmake-boilerplate that runs clang-tidy during a normal build?
I can take a shot at fixing all the warnings, as I'm using clangd in VSCode that's fairly easy.
See #411.
@rjoomen The MR was merged but there are still errors during the build.
Can you merge this, so my next shot at fixing the clang-tidy errors will run the CI I'm trying to pass (I can't merge, because required CI checks do not pass and I do not have enough rights to merge anyway)?
See #412.
@rjoomen Still a few clang-tidy errors in trajopt_common/src/utils.cpp.
See #414.
It looks like the Noble build is failing because of clang-tidy errors, @rjoomen How do you think we should address this? Currently in Tesseract we run clang-tidy separately to avoid this issue.