The best way is to provide a minimal example that illustrates the issue in a small repo on GitHub. This way, I can probably run it on my machine and solve it locally.
If you can't create it, please provide a full log output from the plugin. Without it I cannot do anything. To capture the log:
set "verbose": true in plugin settings
restart Sublime Text
open the file or do the action that causes trouble
open console with Ctrl+P
copy full output to a text file and link it to this issue
Excerpt from huge compile_commands.json located at "/Users/till/Development/mesos-private/build", created using Bear:
ECC assumed the base path to be the location of the compile_commands.json file - which is, as mentioned above "/Users/till/Development/mesos-private/build".
That assumption is incorrect as the base path should not allways be the location of compile_commands.json but, if available, the entry directory of that compile_commands.json record - that would be "/Users/till/Development/mesos-private/build/src" in my example. Hence the correct flags argument would be:
Please do this before submitting:
Please state the following:
3 build 3142
10.13 Beta (17A358a)
What I need to help you:
"verbose": true
in plugin settingsExcerpt from huge compile_commands.json located at "/Users/till/Development/mesos-private/build", created using Bear:
Output from verbose logging:
Note how for example the include original compile_commands.json entry argument:
Gets transformed into the flags argument:
ECC assumed the base path to be the location of the compile_commands.json file - which is, as mentioned above "/Users/till/Development/mesos-private/build".
That assumption is incorrect as the base path should not allways be the location of compile_commands.json but, if available, the entry
directory
of that compile_commands.json record - that would be "/Users/till/Development/mesos-private/build/src" in my example. Hence the correct flags argument would be:See https://clang.llvm.org/docs/JSONCompilationDatabase.html#format for more.