LSP-clangd
C/C++ support for Sublime's LSP plugin provided through clangd.
Details
Installs
- Total 21K
- Win 9K
- Mac 4K
- Linux 9K
| Oct 28 | Oct 27 | Oct 26 | Oct 25 | Oct 24 | Oct 23 | Oct 22 | Oct 21 | Oct 20 | Oct 19 | Oct 18 | Oct 17 | Oct 16 | Oct 15 | Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | Oct 6 | Oct 5 | Oct 4 | Oct 3 | Oct 2 | Oct 1 | Sep 30 | Sep 29 | Sep 28 | Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | Sep 21 | Sep 20 | Sep 19 | Sep 18 | Sep 17 | Sep 16 | Sep 15 | Sep 14 | Sep 13 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 21 | 16 | 12 | 12 | 14 | 19 | 15 | 8 | 12 | 8 | 11 | 14 | 13 | 13 | 17 | 27 | 8 | 7 | 9 | 11 | 12 | 14 | 6 | 11 | 14 | 11 | 12 | 10 | 6 | 16 | 9 | 10 | 12 | 13 | 16 | 13 | 20 | 18 | 9 | 11 | 11 | 8 | 6 | 19 | 5 | 6 |
| Mac | 1 | 2 | 5 | 1 | 2 | 4 | 5 | 5 | 3 | 4 | 4 | 3 | 5 | 6 | 7 | 6 | 2 | 4 | 4 | 3 | 4 | 2 | 0 | 6 | 7 | 10 | 4 | 6 | 6 | 1 | 3 | 2 | 7 | 3 | 6 | 8 | 1 | 6 | 5 | 6 | 5 | 2 | 4 | 3 | 3 | 3 |
| Linux | 11 | 9 | 12 | 13 | 9 | 16 | 10 | 7 | 10 | 11 | 11 | 15 | 11 | 12 | 8 | 21 | 22 | 11 | 10 | 7 | 11 | 5 | 16 | 8 | 12 | 13 | 11 | 15 | 7 | 12 | 6 | 19 | 11 | 10 | 9 | 12 | 20 | 9 | 6 | 7 | 7 | 9 | 6 | 16 | 9 | 8 |
Readme
- Source
- raw.githubusercontent.com
LSP-clangd
C/C++ and Objective-C/C++ support for Sublime's LSP plugin provided through clangd.
Installation
- Install LSP and
LSP-clangdfrom Package Control - (Optional) Install clangd using your package manager or let this package install clangd for you
Usage
By default, clangd will assume your code is built as clang some_file.cc, and you’ll probably get errors about missing #included files, etc.
For complex projects, clangd needs to know your build flags. This can be done using a compile_commands.json or compile_flags.txt file.
For CMake-based projects a compile_commands.json file can be generated using the -DCMAKE_EXPORT_COMPILE_COMMANDS=1 flag.
cd build
cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=1 ..
# compile_commands.json will be written to your build directory.
If your build directory is equivalent to the root of the project or <project_root>/build then clangd will find it. Otherwise, symlink or copy it to the root of your project.
See clangd Project Setup for more information on using
compile_commands.json,compile_flags.txtand other build systems.
Configuration
Here are some ways to configure the package and the language server.
- From
Preferences > Package Settings > LSP > Servers > LSP-clangd - From the command palette:
Preferences: LSP-clangd Settings - Project-specific configuration.
From the command palette run
Project: Edit Projectand add your settings in:
{
"settings": {
"LSP": {
"clangd": {
"initializationOptions": {
// Put your settings here eg.
// "clangd.header-insertion": "iwyu",
}
}
}
}
}
Sublime Commands
| Sublime Command | Description |
|---|---|
lsp_clangd_switch_source_header |
Switch between the main source file (.cpp) and header (.h). |