Downloads of v 0.20201025:


Last Update:

23 Nov 2020

Package Maintainer(s):

Software Author(s):

  • MaskRay


cpp language-server-protocol ide lsp-server


  • 1
  • 2
  • 3

0.20201025 | Updated: 23 Nov 2020



Downloads of v 0.20201025:



Software Author(s):

  • MaskRay

  • 1
  • 2
  • 3
ccls 0.20201025

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install ccls, run the following command from the command line or from PowerShell:


To upgrade ccls, run the following command from the command line or from PowerShell:


To uninstall ccls, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade ccls -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ccls -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure ccls installed
    name: ccls
    state: present
    version: 0.20201025
    source: STEP 3 URL

See docs at

chocolatey_package 'ccls' do
  action    :install
  version  '0.20201025'
  source   'STEP 3 URL'

See docs at

    Name: ccls,
    Version: 0.20201025,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller ccls
   Name     = 'ccls'
   Ensure   = 'Present'
   Version  = '0.20201025'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'ccls':
  provider => 'chocolatey',
  ensure   => '0.20201025',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install ccls version="0.20201025" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved by moderator flcdrg on 12 Dec 2020.


ccls, which originates from cquery, is a C/C++/Objective-C language server.

  • code completion (with both signature help and snippets)
  • definition/references, and other cross references
  • cross reference extensions: $ccls/call $ccls/inheritance $ccls/member $ccls/vars ...
  • formatting
  • hierarchies: call (caller/callee) hierarchy, inheritance (base/derived) hierarchy, member hierarchy
  • symbol rename
  • document symbols and approximate search of workspace symbol
  • hover information
  • diagnostics and code actions (clang FixIts)
  • semantic highlighting and preprocessor skipped regions
  • semantic navigation: $ccls/navigate

It has a global view of the code base and support a lot of cross reference features, see wiki/FAQ.
It starts indexing the whole project (including subprojects if exist) parallelly when you open the first file, while the main thread can serve requests before the indexing is complete.
Saving files will incrementally update the index.

>>> Getting started (CLICK HERE) <<<

choco install ccls

ccls can index itself (~180MiB RSS when idle, noted on 2018-09-01), FreeBSD, glibc, Linux, LLVM (~1800MiB RSS), musl (~60MiB RSS), ... with decent memory footprint. See wiki/Project-Setup for examples.

$ErrorActionPreference = 'Stop';

$version     = $env:chocolateyPackageVersion
$packageName = $env:chocolateyPackageName
$toolsDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$url64       = ''

$packageArgs = @{
    packageName    = $packageName
    unzipLocation  = $toolsDir
    fileType       = 'exe'
    url64bit       = $url64
    checksum64     = '216d78573a43cde06167f601f0180dbdaa4b72031e5299cc144dc839f704b294'
    checksumType64 = 'sha256'

Install-ChocolateyZipPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
ccls 0.20210330 6 Saturday, May 8, 2021 Ready
Discussion for the ccls Package

Ground Rules:

  • This discussion is only about ccls and the ccls package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ccls, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus