I have been using vscode-ccls in my project which is fairly large ( a few GBs ). I have a compile_commands.json setup in my project for CCLS to refer. This works fairly well.
My issue though is that the extension only activates when a C file is opened. Generally this would not be a problem, but if a compile_commands.json is already present, CCLS does not start indexing until a C file is opened. This behaviour extends to .ccls-cache, where the cache isn't loaded until i start working on a C file.
Ideally, to have CCLS start indexing on compile_commands.json/.ccls-cache detection would reduce overall wait time to the user.
I have been using vscode-ccls in my project which is fairly large ( a few GBs ). I have a compile_commands.json setup in my project for CCLS to refer. This works fairly well.
My issue though is that the extension only activates when a C file is opened. Generally this would not be a problem, but if a compile_commands.json is already present, CCLS does not start indexing until a C file is opened. This behaviour extends to .ccls-cache, where the cache isn't loaded until i start working on a C file.
Ideally, to have CCLS start indexing on compile_commands.json/.ccls-cache detection would reduce overall wait time to the user.