llvm-project/clang-tools-extra/clangd/index/remote
Utkarsh Saxena 5bbf6ad5b6 Add an option to fill container for ref
This allows index implementations to fill container details when required specially when computing containerID is expensive.

Differential Revision: https://reviews.llvm.org/D125925
2022-05-19 16:05:38 +02:00
..
marshalling Add an option to fill container for ref 2022-05-19 16:05:38 +02:00
monitor Add 'clangd' prefix to remote index proto targets 2022-01-29 02:20:52 +01:00
server Add 'clangd' prefix to remote index proto targets 2022-01-29 02:20:52 +01:00
unimplemented [clangd] Cleanup dependencies around RemoteIndex 2020-11-04 16:58:11 +01:00
CMakeLists.txt Add 'clangd' prefix to remote index proto targets 2022-01-29 02:20:52 +01:00
Client.cpp [clangd] Rename Features.h -> Feature.h to avoid confilct with libstdc++ 2021-08-06 18:56:41 +02:00
Client.h [clangd] cleanup of header guard names 2021-12-02 15:58:35 +00:00
Index.proto Add an option to fill container for ref 2022-05-19 16:05:38 +02:00
MonitoringService.proto [clangd] Add basic monitoring info request for remote index server 2021-03-16 13:37:58 +01:00
README.md [clangd] Bump recommended gRPC version (1.33.2 -> 1.36.3) 2021-06-07 15:36:33 +02:00
Service.proto [clangd] Add basic monitoring info request for remote index server 2021-03-16 13:37:58 +01:00

README.md

Clangd remote index

Clangd uses a global index for project-wide code completion, navigation and other features. For large projects, building this can take many hours and keeping it loaded uses a lot of memory.

To relieve that burden, we're building remote index — a global index served on a different machine and shared between developers. This directory contains code that is used as Proof of Concept for the upcoming remote index feature.

Building

This feature uses gRPC and Protobuf libraries, so you will need to install them. There are two ways of doing that.

However you install dependencies, to enable this feature and build remote index tools you will need to set this CMake flag — -DCLANGD_ENABLE_REMOTE=On.

System-installed libraries

On Debian-like systems gRPC and Protobuf can be installed from apt:

apt install libgrpc++-dev libprotobuf-dev protobuf-compiler-grpc

Building from sources

Another way of installing gRPC and Protobuf is building from sources using CMake (we need CMake config files to find necessary libraries in LLVM). The easiest way of doing that would be to choose a directory where you want to install so that the installation files are not copied to system root and you can easily uninstall gRPC or use different versions.

# Get source code.
$ git clone -b v1.36.3 https://github.com/grpc/grpc
$ cd grpc
$ git submodule update --init
# Choose directory where you want gRPC installation to live.
$ export GRPC_INSTALL_PATH=/where/you/want/grpc/to/be/installed
# Build and install gRPC to ${GRPC_INSTALL_PATH}
$ mkdir build; cd build
$ cmake -DgRPC_INSTALL=ON -DCMAKE_INSTALL_PREFIX=${GRPC_INSTALL_PATH} -DCMAKE_BUILD_TYPE=Release ..
$ make install

This guide goes into more detail on how to build gRPC from sources.

By default, CMake will look for system-installed libraries when building remote index tools so you will have to adjust LLVM's CMake invocation. The following flag will inform build system that you chose this option — -DGRPC_INSTALL_PATH=${GRPC_INSTALL_PATH}.

Running

You can run clangd-index-server and connect clangd instance to it using --remote-index-address and --project-root flags.