You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project that produces multiple compilation_commands.json files in different folders.
It would be nice if I could set compilationDatabaseDirectory to a list of directories and ccls would read every compilation_commands.json file inside these folders. (Assuming that no *.cpp file has an entry in multiple compilation_commands.json files)
The text was updated successfully, but these errors were encountered:
This would indeed be helpful. Note sure if this is already documented somewhere (haven't read any docs), but for the situation that Volker describes it could also be very handy to somehow support meta-variables for the roots as well.
The use case would be generating the cache at build time and distributing the compiled package, including the cache. At the moment the cache information contains absolute paths that reflect the original build location.
Hello,
I have a project that produces multiple compilation_commands.json files in different folders.
It would be nice if I could set compilationDatabaseDirectory to a list of directories and ccls would read every compilation_commands.json file inside these folders. (Assuming that no *.cpp file has an entry in multiple compilation_commands.json files)
The text was updated successfully, but these errors were encountered: