bazel-compile-commands-extractor
bazel-compile-commands-extractor copied to clipboard
Goal: Enable awesome tooling for Bazel users of the C language family.
In my C++ project the file naming convention is `foo.cc` for source files and `foo.h` for headers, which I think is not too unusual. I was puzzled about why clangd...
**Status:** There's an Apple project to (basically) add Swift support to clangd [here](https://github.com/apple/sourcekit-lsp). It doesn't look mature enough yet (2/2021), but perhaps it will be by the time we'd need...
**Suggested Workaround:** Click the quick fix for now. Sorry; I want it, too. **Status:** We'd need clangd (and its editor plugins) to do this, I think. Filed [an issue](https://github.com/clangd/clangd/issues/656) about...
**Suggested Workaround:** You should, but you'll have to do this in your head for now. At least there's autocomplete for everything you want to use--the issue is that there's also...
Hey all! Self-filing an issue to collect interest and feedback. Some people have been using this tool and compile_commands.json to run clang-tidy from the command line. [Clang-tidy can also run...
Bazel's working on a new external dependency management system called Bazelmod, [arriving in 6.0 and by default in 7.0, replacing and deprecating the WORKSPACE](https://github.com/bazelbuild/bazel/issues/13316#issuecomment-1138630271). Please chime in if you're looking...
Hey, I've bumped into a case where the c++ standard flag is not correctly passed into *compile_commands.json* file. My *.bazelrc* looks like: ``` test --test_output=errors build -c opt --cxxopt='-std=c++17' ```...
Hi First, thank you for creating this fantastic tool! Are there any plans to support a custom `output_user_root`? I am currently facing an issue with this because we use the...
https://github.com/mvukov/optimus/pull/81: This is what I get on my local machine w/ Ubuntu 22.04 (I also got the same error or another machine w/ the same OS). ``` bazel run //:refresh_compile_commands...
I've had a setup evolve so that it is now using a `bazelrc` in a custom location (i.e. `bazel --bazelrc=/path/to/.bazelrc ...` is now how all of my commands are run)....