LSP-clangd
C/C++ support for Sublime's LSP plugin provided through clangd.
Details
Installs
- Total 21K
- Win 9K
- Mac 4K
- Linux 8K
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 | Sep 12 | Sep 11 | Sep 10 | Sep 9 | Sep 8 | Sep 7 | Sep 6 | Sep 5 | Sep 4 | Sep 3 | Sep 2 | Sep 1 | Aug 31 | Aug 30 | Aug 29 | Aug 28 | Aug 27 | Aug 26 | Aug 25 | Aug 24 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 6 | 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 | 12 | 15 | 10 | 16 | 10 | 11 | 8 | 8 | 14 | 13 | 12 | 12 | 10 | 10 | 25 | 12 | 12 | 17 | 14 | 11 |
Mac | 2 | 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 | 8 | 6 | 3 | 1 | 2 | 4 | 4 | 6 | 2 | 6 | 9 | 9 | 1 | 3 | 5 | 3 | 6 | 1 | 5 | 6 |
Linux | 2 | 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 | 10 | 9 | 11 | 13 | 9 | 10 | 15 | 14 | 6 | 13 | 10 | 14 | 9 | 6 | 10 | 8 | 5 | 9 | 10 | 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-clangd
from 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 #include
d 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.txt
and 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 Project
and 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). |