Paul Smith

Yes, I thought of that as well. It might be a good idea. A downside is that the contents of that directory (for my ccls which is built with Clang...

As for zipping: yes that would help but of course now you've introduced a new dependency to build the project to link in libz or some other compression library, which...

@gromgit @carlocab If you check the thread for this issue you'll see that it's not correct to look up the resource dir at runtime. The resource dir that ccls uses...

I don't know much about brew (or MacOS in general) so I can't say what's right or wrong: if it works great. Hopefully there are appropriate dependency relationships documented so...

The only thing you need to distribute is the `ccls` binary, plus the files in the resource directory. When I build ccls it's statically linked with the clang libraries and...

Why generate a hash? ccls already places the cache for a given path in a directory which is named by the fully-qualified path to that directory. it replaces "/" with...

It seems to me that everything you want can be achieved already: see https://github.com/MaskRay/ccls/wiki/Customization#cachedirectory Is there something needed that is not possible?

Just to point out: the problem with using a separate cache directory is cleanup. If the cache directory is inside the workspace then when you delete the workspace (suppose you...

I guess I'm not sure what you mean by "git root doesn't exist". How can the code be available if the Git root doesn't exist? Maybe you mean, use XDG...

I wasn't able to reproduce this, but I'm pretty sure this is not right: ``` %h -x %h c++-header ``` According to the Clang documentation the argument to `-x` is...