-
This would allow people to use choose [clangd as the language server](https://github.com/platformio/platformio-vscode-ide/issues/1940), get clang-tidy warnings in real-time and use other tools based o…
-
The VS Code extension currently check for the presence of `Package.swift` or `compile_commands.json` in `isValidWorkspaceFolder`. SourcKit-LSP can also handle `compile_flags.txt` (https://clang.llvm.o…
-
The clangd extension supports specifying a compile_commands.json file which specifies the compiler arguments that are used to build each source file. The system that vscode-clang-tidy uses of requirin…
jwatt updated
2 years ago
-
### Description of the bug:
In our large codebase, we use includes = [] to declare an include path for all dependees of a cc_-target. We either:
1) Declare an include path for headers in the w…
-
**Describe the bug**
I'm using MacOS and cross-compiling an ARM project using GNU GCC compiler.
**To Reproduce**
Not easy to reproduce on your side because you need to do a big amount of work to …
-
I have a large-ish project that uses different build directories for different build types.
For example, a simple vscode `settings.json` could look like,
```
{
"cmake.buildDirectory": "$…
-
Hi,
I'm having issues using the generated the output from the `compilation-database` subtarget, which seems to boil down to clangd not liking relative `directory` fields.
Here's how to reproduce…
-
Bug type: General
**Describe the bug**
- OS and Version: Latest Linux Mint
- VS Code Version: 1.61
- C/C++ Extension Version: v1.7.0
This bug should be pretty easy to reproduce, for example:
…
-
### Description of problem
I'm about to make my first small contribution to Dokku and tried running the test suite locally on a fresh clone first.
Unfortunately, test fail with "No pack binary f…
-
Hello! I've discussed this a bit over in https://github.com/emscripten-core/emscripten/issues/19273 and felt it made more sense to bring the issue over here. (for context, I felt this because the **co…