Closed Artalus closed 6 years ago
Hi @Artalus , Thanks for reporting this. Could you please test locally with the latest master.
Also, note that several improvements/features/changes have been implemented since version 0.9.2, for example:
compile_commands.json
if it exists (unless -f
is used) instead of rewriting it entirely always, this is particularly useful when running non clean builds with changes in flags/source files, so the compiledb
is almost(?) ready to be used as a real make wrapper.strict
mode, which ignore source files which do not exist in the file system (If desired one can disable those checkings using -S
option, useful for example when processing build logs where the actual code base is not on the host's file system.Thank you, it works fine now. Only I thought the joined command
string was considered a feature, not a regression that should be removed completely, but this one is up to you and clang-tools compliance :)
I used
compiledb
for a while to analyze Makefiles produced by our legacy build system. It was very convenient sincecompile_commands.json
file contained separate fieldarguments: []
which I could then grep usingjq
. After recent update0.9.2 -> 0.9.7
my scripts broke down since nowcompiledb
just copies whole long compile command into a singlecommand
field. It would be nice to have an option to addarguments
array to the output.