what I was meaning: please keep a tag assigned to one commit
and don't change it ever again in the future
it is okay if an old release no longer builds with a new compiler version
that's when you create a new point release in a maintenance branch
I intended to create 0.20190314.4 but probably modified 0.20190823.4 unintentionally
that tag now points to very recent commits in contrast to what is around there
and FTR
0.20190314.5 is no longer on master :-(
argh, yeah mixed them up again
I meant
0.20190823.5
0.20190823.5 has changed either. https://github.com/MaskRay/ccls/releases/tag/0.20190823.5 = https://github.com/condy0919/ccls/releases/tag/0.20190823.5
Hey! I seem to be doing something stupid. ccls seems to be parsing all my .h files as C (as opposed to cpp, even if a corresponding .cpp files exists). I tried to add these lines to my .ccls file:
%h -x
%h c++-headerwith no luck, I'm still getting unknown type name 'class'. Is there anything else I could try?
The only way I can get around this currently is to rename the
.h file to .hpp but that doesn't seem optimal to me (just for consistency with all the other libraries that I'm using and for which that doesn't seem to be a problem). For a little context, I'm using the auto-generated .ccls file provided by platformio
Hi not sure where to post this but i'll place it here. Just want to advise the contributors that i have found and fixed a potential issue. ccls has been crashing on me, upon further investigation I discovered that the --resource-dir parameter was incorrect. It was pointing to /usr/lib64/clang/9.0 instead of version 10.0.0. I have updated from fedora 31 to 32 (i.e. by way of the os update script)
omit your build/ directory or move it outside of your projects root dir
if you just want ccls to parse some types of files, you can pass one or more regexs to initialBlacklist
I thought that's what
%h c++-header is supposed to do
Anyone have issues with CCLS timing out when using pre-compiled headers?
I'm specifically using Cmake's target_precompile_headers with Coc-nvim (on neovim).
The precompiled headers are correctly building, but any time I start browsing files, ccls times out instead of doing anything.
It stops recommending fixes, showing errors, etc. It's like it's just off.
But then I simply comment out the target_precompile_headers and re-build with cmake, and all of a sudden it's working as expected.
I'm using the coc-settings.json recommended in the coc wiki, if it matters.
Hi I am trying to build ccls on a debian box without any root permission and which does not have ncurses library builtin. I have manually built in the ncurses library. I have set the LD_LIBRARY_PATH, but build does not recognize libnucurses.so (6.1) from this directory. How do you manually provide the location of the ncurses library to ccls.
not on my machine:
ldd /usr/bin/ccls
linux-vdso.so.1 (0x00007ffc86326000)
libclang-cpp.so.10 => /usr/lib64/libclang-cpp.so.10 (0x00007fa9c35c9000)
libLLVM.so.10 => /usr/lib64/libLLVM.so.10 (0x00007fa9be779000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fa9be5a3000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa9be589000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa9be567000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa9be3a1000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa9c67e0000)
libedit.so.0 => /usr/lib64/../lib64/libedit.so.0 (0x00007fa9be365000)
libz.so.1 => /lib64/libz.so.1 (0x00007fa9be34b000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa9be346000)
libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007fa9be315000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa9be1cf000)
libxml2.so.2 => /usr/lib64/../lib64/libxml2.so.2 (0x00007fa9be066000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fa9be028000)
/env_build/cmake/CMake/bin/cmake --build Release
[ 2%] Linking CXX executable ccls
/usr/bin/ld: cannot find -lncurses
collect2: error: ld returned 1 exit status
CMakeFiles/ccls.dir/build.make:733: recipe for target 'ccls' failed
make[2]: [ccls] Error 1
CMakeFiles/Makefile2:136: recipe for target 'CMakeFiles/ccls.dir/all' failed
make[1]: [CMakeFiles/ccls.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: * [all] Error 2
kangyas@rpcs02: ~/env_build/ccls (master) $
[ 2%] Linking CXX executable ccls
/usr/bin/ld: cannot find -lncurses
collect2: error: ld returned 1 exit status
CMakeFiles/ccls.dir/build.make:733: recipe for target 'ccls' failed
make[2]: [ccls] Error 1
CMakeFiles/Makefile2:136: recipe for target 'CMakeFiles/ccls.dir/all' failed
make[1]: [CMakeFiles/ccls.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: * [all] Error 2
kangyas@rpcs02: ~/env_build/ccls (master) $
ah, wait you're building the master branch?
@MaskRay Some time ago I have been trying to build ccls on CentOS and you told me If I make it work to give you an update. So in order to make it work I built a newer gcc(9.1) and also built clang(10.0.0) and with some missing packages from the package manager the master branch ccls built successfully. So when I find some free time I am going to update the wiki on how to build ccls on Centos.
I am having trouble configuring ccls with coc.nvim
I use Arch Linux, and installed ccls using "pacman -S ccls"
Followed these instructions and tried first example: https://github.com/MaskRay/ccls/wiki/coc.nvim
{
"diagnostic.infoSign": "--",
"diagnostic.displayByAle": true,
"typescript.showUnused": false,
"javascript.showUnused": false,
"languageserver": {
"ccls": {
"command": "ccls",
"filetypes": ["c", "cpp", "cuda", "objc", "objcpp"],
"rootPatterns": [".ccls-root", "compile_commands.json"],
"initializationOptions": {
"cache": {
"directory": ".ccls-cache"
},
"client": {
"snippetSupport": true
},
"completion": {
"placeholder": true
}
}
}
}
}
Here is my
:CocConfig