LSP-clangd
C/C++ support for Sublime's LSP plugin provided through clangd.
Details
Installs
- Total 17K
- Win 7K
- Mac 3K
- Linux 7K
Apr 24 | Apr 23 | Apr 22 | Apr 21 | Apr 20 | Apr 19 | Apr 18 | Apr 17 | Apr 16 | Apr 15 | Apr 14 | Apr 13 | Apr 12 | Apr 11 | Apr 10 | Apr 9 | Apr 8 | Apr 7 | Apr 6 | Apr 5 | Apr 4 | Apr 3 | Apr 2 | Apr 1 | Mar 31 | Mar 30 | Mar 29 | Mar 28 | Mar 27 | Mar 26 | Mar 25 | Mar 24 | Mar 23 | Mar 22 | Mar 21 | Mar 20 | Mar 19 | Mar 18 | Mar 17 | Mar 16 | Mar 15 | Mar 14 | Mar 13 | Mar 12 | Mar 11 | Mar 10 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 8 | 8 | 12 | 12 | 13 | 11 | 9 | 18 | 9 | 11 | 5 | 14 | 14 | 18 | 15 | 14 | 20 | 8 | 10 | 9 | 9 | 9 | 6 | 14 | 7 | 14 | 10 | 10 | 9 | 12 | 12 | 11 | 5 | 4 | 5 | 12 | 6 | 21 | 11 | 7 | 7 | 15 | 15 | 17 | 12 | 7 |
Mac | 3 | 6 | 6 | 3 | 1 | 7 | 5 | 2 | 5 | 6 | 7 | 2 | 7 | 4 | 4 | 2 | 7 | 8 | 2 | 3 | 6 | 3 | 2 | 4 | 5 | 3 | 6 | 4 | 6 | 7 | 4 | 6 | 3 | 2 | 5 | 10 | 3 | 6 | 4 | 8 | 6 | 5 | 1 | 1 | 2 | 4 |
Linux | 10 | 7 | 9 | 8 | 9 | 12 | 9 | 5 | 11 | 10 | 5 | 10 | 8 | 9 | 11 | 13 | 10 | 10 | 7 | 9 | 7 | 10 | 7 | 5 | 14 | 12 | 12 | 15 | 8 | 12 | 2 | 10 | 13 | 7 | 17 | 9 | 9 | 10 | 12 | 7 | 11 | 8 | 8 | 19 | 7 | 10 |
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). |