C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
Go to file
2018-01-18 15:14:36 -08:00
src Fix serializer MSVC C4244 2018-01-18 11:22:36 -08:00
third_party Add missing header files in siphash.c, fix #301 2018-01-16 12:49:08 -08:00
.appveyor.yml Fix AppVeyor 2018-01-07 02:51:26 -08:00
.clang_complete Misc formatting 2017-03-17 00:58:41 -07:00
.clang-format Add project .clang-format 2017-11-19 12:15:14 -05:00
.gitattributes Index tests need to be CRLF 2018-01-03 17:22:21 -08:00
.gitignore Moved lines above 2018-01-12 09:36:17 -08:00
.gitmodules Add submodule https://github.com/msgpack/msgpack-c and make Serialize/Deserialize aware of SerializeFormat 2018-01-06 15:29:53 -08:00
.pep8 wip 2017-12-28 08:55:46 -08:00
.travis.yml travis: macOS is optional 2018-01-18 10:25:08 -08:00
.ycm_extra_conf.py Add src/ directory to .ycm_extra_conf.py 2017-12-07 11:54:51 -08:00
compile_commands.json Update compile_commands.json symlink to point to build/release 2017-12-12 00:10:20 -08:00
README.md [emacs] redirect to https://github.com/cquery-project/emacs-cquery and clean up README 2018-01-18 15:14:36 -08:00
wscript Add a comment explaining part of the build script 2018-01-18 14:49:34 -08:00

cquery

Join the chat at https://gitter.im/cquery-project/Lobby

cquery is a highly-scalable, low-latency language server for C/C++/Objective-C. It is tested and designed for large code bases like Chromium. cquery provides accurate and fast semantic analysis without interrupting workflow.

Demo

cquery implements almost the entire language server protocol and provides some extra features to boot:

  • code completion (with both signature help and snippets)
  • finding definition/references
  • type hierarchy (parent type, derived types, expandable tree view)
  • finding base/derived methods/classes, call tree
  • symbol rename
  • document and global symbol search
  • hover tooltips showing symbol type
  • diagnostics
  • code actions (clang FixIts)
  • darken/fade code disabled by preprocessor
  • #include auto-complete, undefined type include insertion, include quick-jump (goto definition, document links)
  • auto-implement functions without a definition
  • semantic highlighting, including support for rainbow semantic highlighting

Setup - build cquery, install extension, setup project

There are three steps to get cquery up and running. Eventually, cquery will be published in the vscode extension marketplace which will reduce these three steps to only project setup.

Getting started

And wiki/Build.

Install extension

cquery includes a vscode extension; it is released in https://github.com/jacobdufault/cquery/releases. Launch vscode and install the vscode-extension.vsix extension. To do this:

  • Hit F1; execute the command Install from VSIX.
  • Select vscode-extension.vsix in the file chooser.

IMPORTANT: Please reinstall the extension when you download it - it is still being developed.

See the wiki for additional details on setting up the extension.

If you run into issues, you can view debug output by running the (F1) View: Toggle Output command and opening the cquery output section.

Project setup

compile_commands.json (Best)

See wiki for how to generate compile_commands.json with CMake, Build EAR, Ninja, ...

If the compile_commands.json is not in the top-level workspace directory, then the cquery.misc.compilationDatabaseDirectory setting can be used to specify its location.

cquery.index.extraClangArguments

If for whatever reason you cannot generate a compile_commands.json file, you can add the flags to the cquery.index.extraClangArguments configuration option.

.cquery

If for whatever reason you cannot generate a compile_commands.json file, you can add the flags to a file called .cquery located in the top-level workspace directory.

Each argument in that file is separated by a newline. Lines starting with # are skipped. The first line can optionally be the path to the intended compiler, which can help if the standard library paths are relative to the binary. Here's an example:

# Driver
/usr/bin/clang++-4.0

# Language
-xc++
-std=c++11

# Includes
-I/work/cquery/third_party

Building extension

If you wish to modify the vscode extension, you will need to build it locally. Luckily, it is pretty easy - the only dependency is npm.

# Build extension
$ cd vscode-client
$ npm install
$ code .

When VSCode is running, you can hit F5 to build and launch the extension locally.

Limitations

cquery is able to respond to queries quickly because it caches a huge amount of information. When a request comes in, cquery just looks it up in the cache without running many computations. As a result, there's a large memory overhead. For example, a full index of Chrome will take about 10gb of memory. If you exclude v8, webkit, and third_party, it goes down to about 6.5gb.

Wiki

For Emacs/Vim/other editors integration and some additional tips, see wiki.

Chromium tips

Chromium is a very large codebase, so cquery benefits from a bit of tuning. Optionally add these to your settings:

  // Set slightly lower than your CPU core count to keep other tools responsive.
  "cquery.misc.indexerCount": 50,
  // Remove uncommonly used directories with large numbers of files.
  "cquery.index.blacklist": [
   ".*/src/base/third_party/.*",
   ".*/src/native_client/.*",
   ".*/src/native_client_sdk/.*",
   ".*/src/third_party/.*",
   ".*/src/v8/.*",
   ".*/src/webkit/.*"
  ]

License

MIT